Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbfd6c9edf3d814365d82cfe13d140147735bd90279f130ff56ed94b5360f4ee

Tx prefix hash: 8a6389992f385f71aab929c79c7a4dd3e72774bc4af73b73b341beba49eaeaea
Tx public key: 0c2113473750d0e2eb8a862df896a37720d0dffda8020a76c4213d3bf5e33f18
Timestamp: 1706056241 Timestamp [UCT]: 2024-01-24 00:30:41 Age [y:d:h:m:s]: 01:105:15:50:37
Block: 941927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336622 RingCT/type: yes/0
Extra: 010c2113473750d0e2eb8a862df896a37720d0dffda8020a76c4213d3bf5e33f180211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4901613be1cb92e5fd0c3d60473df9d3f837bed7edda45f163821efb2335a39 0.600000000000 1400085 of 15

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": 941937, "vin": [ { "gen": { "height": 941927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4901613be1cb92e5fd0c3d60473df9d3f837bed7edda45f163821efb2335a39" } } ], "extra": [ 1, 12, 33, 19, 71, 55, 80, 208, 226, 235, 138, 134, 45, 248, 150, 163, 119, 32, 208, 223, 253, 168, 2, 10, 118, 196, 33, 61, 59, 245, 227, 63, 24, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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