Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656e8ce7c0a124f34e1b159644802999865bc5f71c9e7dbaf089baaf3d230e97

Tx prefix hash: e4bd6416584efb677ad0d7ca5a332a8116b5b73fa267a5e8c0532ae366c4d0af
Tx public key: 339fac9a23c70bffc0b88f916a798451c579fcab8eb7859446e67d73673b3b02
Timestamp: 1718288417 Timestamp [UCT]: 2024-06-13 14:20:17 Age [y:d:h:m:s]: 00:275:11:04:48
Block: 1043367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196858 RingCT/type: yes/0
Extra: 01339fac9a23c70bffc0b88f916a798451c579fcab8eb7859446e67d73673b3b020211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9f3df7bc978fdb3fb52eec3f271bcd57e7f698cf92849616e895bd92d7ebda9 0.600000000000 1512504 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": 1043377, "vin": [ { "gen": { "height": 1043367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9f3df7bc978fdb3fb52eec3f271bcd57e7f698cf92849616e895bd92d7ebda9" } } ], "extra": [ 1, 51, 159, 172, 154, 35, 199, 11, 255, 192, 184, 143, 145, 106, 121, 132, 81, 197, 121, 252, 171, 142, 183, 133, 148, 70, 230, 125, 115, 103, 59, 59, 2, 2, 17, 0, 0, 0, 1, 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