Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c089ab77f80e2e04fcaf4b3ea1a3b1e454b96fb0e69512e818b881b11947f469

Tx prefix hash: b12f890b0b332650cb9b1ce5ed5d2126d89adce2a0cf3cd55b9c5bb0bd848ffe
Tx public key: 9635e809d9892a1756e665df7ce062c5819df2532d0d2aa37479f98abecb504d
Timestamp: 1731611268 Timestamp [UCT]: 2024-11-14 19:07:48 Age [y:d:h:m:s]: 00:218:22:21:12
Block: 1153734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156162 RingCT/type: yes/0
Extra: 019635e809d9892a1756e665df7ce062c5819df2532d0d2aa37479f98abecb504d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd4adc0fbddc67b5550e4b438c05df0d918b9d2b890f0a03378a5f1ee198b4e7 0.600000000000 1639345 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": 1153744, "vin": [ { "gen": { "height": 1153734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd4adc0fbddc67b5550e4b438c05df0d918b9d2b890f0a03378a5f1ee198b4e7" } } ], "extra": [ 1, 150, 53, 232, 9, 217, 137, 42, 23, 86, 230, 101, 223, 124, 224, 98, 197, 129, 157, 242, 83, 45, 13, 42, 163, 116, 121, 249, 138, 190, 203, 80, 77, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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