Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf21779767631b5b953d14f29f7ff4e04f1c79d8546806e59ef6d8731e47cad0

Tx prefix hash: 2334b83f7dcd89e5065e10330f87f077c71e8a4834dc1ccd733d0fbfca0e7c93
Tx public key: 4611f54e4bce7400152d4fb53c67fae30a0605f6b9b4c9c17e9137dfee2a0512
Timestamp: 1632431976 Timestamp [UCT]: 2021-09-23 21:19:36 Age [y:d:h:m:s]: 02:251:22:31:58
Block: 339656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 695288 RingCT/type: yes/0
Extra: 014611f54e4bce7400152d4fb53c67fae30a0605f6b9b4c9c17e9137dfee2a05120211000000753fc41461000000000000000000

1 output(s) for total of 45.981073542000 dcy

stealth address amount amount idx
00: c9f52fb7288a7281ef13a0373d55d36ce4a3198d23a560b2994970fed1e734c9 45.981073542000 698471 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": 339666, "vin": [ { "gen": { "height": 339656 } } ], "vout": [ { "amount": 45981073542, "target": { "key": "c9f52fb7288a7281ef13a0373d55d36ce4a3198d23a560b2994970fed1e734c9" } } ], "extra": [ 1, 70, 17, 245, 78, 75, 206, 116, 0, 21, 45, 79, 181, 60, 103, 250, 227, 10, 6, 5, 246, 185, 180, 201, 193, 126, 145, 55, 223, 238, 42, 5, 18, 2, 17, 0, 0, 0, 117, 63, 196, 20, 97, 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