Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63f1333a2ef279b8f05e786cf7f6254033974d13ef10382f9622cf647b2e55a6

Tx prefix hash: 9a21484a4077a3b6f7605fc66e5da3d2bd40f905f4198f40e8d0ad2058d3dccb
Tx public key: 87e657af82c04e0469e452f952db8e4c82e6bd1710d8a421c9e86fe56d2f549a
Timestamp: 1715079857 Timestamp [UCT]: 2024-05-07 11:04:17 Age [y:d:h:m:s]: 00:189:23:39:12
Block: 1016768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135991 RingCT/type: yes/0
Extra: 0187e657af82c04e0469e452f952db8e4c82e6bd1710d8a421c9e86fe56d2f549a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e6c4b10ea35ad924d85ded54d1622bbe384578e500f8e5daf0e0fedc54dae13 0.600000000000 1480445 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": 1016778, "vin": [ { "gen": { "height": 1016768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e6c4b10ea35ad924d85ded54d1622bbe384578e500f8e5daf0e0fedc54dae13" } } ], "extra": [ 1, 135, 230, 87, 175, 130, 192, 78, 4, 105, 228, 82, 249, 82, 219, 142, 76, 130, 230, 189, 23, 16, 216, 164, 33, 201, 232, 111, 229, 109, 47, 84, 154, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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