Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 92399bf8c47bdabb64f7a117888d3209c311b30825b1e4aba6e16afe2b92cd7c

Tx prefix hash: f7caafb3b427863398c2233329d0145c02c3ab211dfef822a1486bb6341b33fd
Tx public key: 75364ca9a374d9a52cc691f99605aef892eaceacedf23e48732bfa72a57c40a7
Timestamp: 1648844638 Timestamp [UCT]: 2022-04-01 20:23:58 Age [y:d:h:m:s]: 02:347:19:41:25
Block: 471160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 768073 RingCT/type: yes/0
Extra: 0175364ca9a374d9a52cc691f99605aef892eaceacedf23e48732bfa72a57c40a70211000000155eb576c5000000000000000000

1 output(s) for total of 16.859767447000 dcy

stealth address amount amount idx
00: 2d01da30979f9d66f31bde25b1775110b773e50e425461e7b5cbdaead4c9d914 16.859767447000 890444 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 471170, "vin": [ { "gen": { "height": 471160 } } ], "vout": [ { "amount": 16859767447, "target": { "key": "2d01da30979f9d66f31bde25b1775110b773e50e425461e7b5cbdaead4c9d914" } } ], "extra": [ 1, 117, 54, 76, 169, 163, 116, 217, 165, 44, 198, 145, 249, 150, 5, 174, 248, 146, 234, 206, 172, 237, 242, 62, 72, 115, 43, 250, 114, 165, 124, 64, 167, 2, 17, 0, 0, 0, 21, 94, 181, 118, 197, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8