Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 288ec069231225e23d57177a65545f026e1c275a63c549494da33cf8094e2327

Tx prefix hash: 3744e20b0c3b661957807753f7613a37604019e341d899228733905c550f7ef0
Tx public key: 3a5083e42c309b58e71bd8aeee9255ab8eb618bdcb464c4a7a7955b404b6be50
Timestamp: 1728251847 Timestamp [UCT]: 2024-10-06 21:57:27 Age [y:d:h:m:s]: 00:173:17:29:33
Block: 1125968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123952 RingCT/type: yes/0
Extra: 013a5083e42c309b58e71bd8aeee9255ab8eb618bdcb464c4a7a7955b404b6be5002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ca460b6f07d4663a39d6c6de39dc95b3347e28deac8f8dc5d234b862dcdb310 0.600000000000 1608741 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": 1125978, "vin": [ { "gen": { "height": 1125968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ca460b6f07d4663a39d6c6de39dc95b3347e28deac8f8dc5d234b862dcdb310" } } ], "extra": [ 1, 58, 80, 131, 228, 44, 48, 155, 88, 231, 27, 216, 174, 238, 146, 85, 171, 142, 182, 24, 189, 203, 70, 76, 74, 122, 121, 85, 180, 4, 182, 190, 80, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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