Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9fb96113041e82f375e3d169dcfca8184da6eaa37c4c7a563accf9e33fe196b

Tx prefix hash: ab62c265a23d6e7fa8a1a4421c461209f386ef2de7abae3e0b33d7972843ae53
Tx public key: c7bd59590131284f70f9f74f170fff507cb1c261be0fc882644e0bcc5c43d827
Timestamp: 1714322267 Timestamp [UCT]: 2024-04-28 16:37:47 Age [y:d:h:m:s]: 00:354:14:44:29
Block: 1010476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253514 RingCT/type: yes/0
Extra: 01c7bd59590131284f70f9f74f170fff507cb1c261be0fc882644e0bcc5c43d82702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c72de25249172ed93350e37847da0ab7e7d346ed704e7343209d6f81de555f0 0.600000000000 1472446 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": 1010486, "vin": [ { "gen": { "height": 1010476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c72de25249172ed93350e37847da0ab7e7d346ed704e7343209d6f81de555f0" } } ], "extra": [ 1, 199, 189, 89, 89, 1, 49, 40, 79, 112, 249, 247, 79, 23, 15, 255, 80, 124, 177, 194, 97, 190, 15, 200, 130, 100, 78, 11, 204, 92, 67, 216, 39, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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