Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9204d7c2f4077f0e2bc32010aa096f62f3680a53853e051c292c7839eb584d7

Tx prefix hash: 8443384350a8274df4a3e1f32652211cf60b8bdd1457defc263c53f662a4153f
Tx public key: 1288fe84ee930cc7b064f98a6c66763d6eeb7f09b3e8a4f78d80fa854a4a8fd6
Timestamp: 1657224823 Timestamp [UCT]: 2022-07-07 20:13:43 Age [y:d:h:m:s]: 03:094:10:14:50
Block: 538834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 847159 RingCT/type: yes/0
Extra: 011288fe84ee930cc7b064f98a6c66763d6eeb7f09b3e8a4f78d80fa854a4a8fd60211000000024da16a3a000000000000000000

1 output(s) for total of 10.060496771000 dcy

stealth address amount amount idx
00: d4364cb131facbd3a446eadc8f4ecde6f822d52641de2c11f2b038afc5fc35d4 10.060496771000 968881 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": 538844, "vin": [ { "gen": { "height": 538834 } } ], "vout": [ { "amount": 10060496771, "target": { "key": "d4364cb131facbd3a446eadc8f4ecde6f822d52641de2c11f2b038afc5fc35d4" } } ], "extra": [ 1, 18, 136, 254, 132, 238, 147, 12, 199, 176, 100, 249, 138, 108, 102, 118, 61, 110, 235, 127, 9, 179, 232, 164, 247, 141, 128, 250, 133, 74, 74, 143, 214, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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