Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c75e512f924d127530c85fbcbb826e456261a68f5c85ea5dc2db35ef8f63b2f8

Tx prefix hash: ee8053105d6869220fa382285c6b7e08f28aeb366a9d6ab82d34444076c2b583
Tx public key: 60eda89e99fd529ce38770a0135d374ae314e19eea9f4168afd1741d49406d52
Timestamp: 1650385321 Timestamp [UCT]: 2022-04-19 16:22:01 Age [y:d:h:m:s]: 03:195:20:52:47
Block: 483675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 918279 RingCT/type: yes/0
Extra: 0160eda89e99fd529ce38770a0135d374ae314e19eea9f4168afd1741d49406d520211000000184da16a3a000000000000000000

1 output(s) for total of 15.324424414000 dcy

stealth address amount amount idx
00: dd9015e8e7dc24d58f9df28a0109f222394d6190dc259dbf09589d8ea62e5ddd 15.324424414000 905396 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": 483685, "vin": [ { "gen": { "height": 483675 } } ], "vout": [ { "amount": 15324424414, "target": { "key": "dd9015e8e7dc24d58f9df28a0109f222394d6190dc259dbf09589d8ea62e5ddd" } } ], "extra": [ 1, 96, 237, 168, 158, 153, 253, 82, 156, 227, 135, 112, 160, 19, 93, 55, 74, 227, 20, 225, 158, 234, 159, 65, 104, 175, 209, 116, 29, 73, 64, 109, 82, 2, 17, 0, 0, 0, 24, 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