Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac4caf046f098b3bdb1289997895459f07904a609a8f389c38d809c31e591ea3

Tx prefix hash: 56c9cbb83df6d6e326ce00d3db0a85c9c17d0cc0c306a7fdd7f058e0d9a070fd
Tx public key: 6c3a9ef50dc234c39fbdbd07f8df8038de55eeeae2aa24afc641b059ee8cca3b
Timestamp: 1706989860 Timestamp [UCT]: 2024-02-03 19:51:00 Age [y:d:h:m:s]: 01:137:00:55:57
Block: 949676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358920 RingCT/type: yes/0
Extra: 016c3a9ef50dc234c39fbdbd07f8df8038de55eeeae2aa24afc641b059ee8cca3b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7526a92c1f495f0578a8643062efa1abd270db2515fde5221775aa7ddaba94c8 0.600000000000 1408206 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": 949686, "vin": [ { "gen": { "height": 949676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7526a92c1f495f0578a8643062efa1abd270db2515fde5221775aa7ddaba94c8" } } ], "extra": [ 1, 108, 58, 158, 245, 13, 194, 52, 195, 159, 189, 189, 7, 248, 223, 128, 56, 222, 85, 238, 234, 226, 170, 36, 175, 198, 65, 176, 89, 238, 140, 202, 59, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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