Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f19740cbcd21b8c5af856a9e9a285f4d400f0ef666e00b90b1aec009c41cbab

Tx prefix hash: e20f6e2c5af2bd66182bde32e84cd752f01a753a879cbf20c62fc2d35edb7418
Tx public key: 2046f70b3684e63e33c55e0006a38dad4d81266d44377ba8d9c11c21683f750e
Timestamp: 1717274200 Timestamp [UCT]: 2024-06-01 20:36:40 Age [y:d:h:m:s]: 01:017:19:45:49
Block: 1034969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273506 RingCT/type: yes/0
Extra: 012046f70b3684e63e33c55e0006a38dad4d81266d44377ba8d9c11c21683f750e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4de74f2f225e85a75d128d3d0e5b06a6a124c46db9ec1687680c296fb229fdb3 0.600000000000 1503488 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": 1034979, "vin": [ { "gen": { "height": 1034969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4de74f2f225e85a75d128d3d0e5b06a6a124c46db9ec1687680c296fb229fdb3" } } ], "extra": [ 1, 32, 70, 247, 11, 54, 132, 230, 62, 51, 197, 94, 0, 6, 163, 141, 173, 77, 129, 38, 109, 68, 55, 123, 168, 217, 193, 28, 33, 104, 63, 117, 14, 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