Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 677d00349b3435b6183aa9fa992547363bde512905dafcf20283e1fd5162c2dc

Tx prefix hash: ad2b2dfa20ebd67c2b562ec6bf29cff8a61335d0ccc4e1fd5fe9ced2fcf57a90
Tx public key: 6abab77cb9b5fc146f2f60c282ecbc167e53f7ddb2029ac0ce178c3721e4ec84
Timestamp: 1703411497 Timestamp [UCT]: 2023-12-24 09:51:37 Age [y:d:h:m:s]: 02:016:09:51:29
Block: 920035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531516 RingCT/type: yes/0
Extra: 016abab77cb9b5fc146f2f60c282ecbc167e53f7ddb2029ac0ce178c3721e4ec840211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4cd1d1b4ad43994d837ac8cf89352ff2a3658e497af67b77fe3181eb1aa1ab3 0.600000000000 1377713 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": 920045, "vin": [ { "gen": { "height": 920035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4cd1d1b4ad43994d837ac8cf89352ff2a3658e497af67b77fe3181eb1aa1ab3" } } ], "extra": [ 1, 106, 186, 183, 124, 185, 181, 252, 20, 111, 47, 96, 194, 130, 236, 188, 22, 126, 83, 247, 221, 178, 2, 154, 192, 206, 23, 140, 55, 33, 228, 236, 132, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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