Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d9a1c7f4258322fe292172e8f862d83efe4d428a5c28058b74abf5ed9670fcd

Tx prefix hash: cbf35114138cb6ee259a51f7ea13d87e225b2262671ae1e92a6073660e055888
Tx public key: 3224021e0a7a2f8fd2819929d80045fd701dbf0a33662fb4d32c279ee55ed33c
Timestamp: 1717030108 Timestamp [UCT]: 2024-05-30 00:48:28 Age [y:d:h:m:s]: 01:017:01:56:14
Block: 1032944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273011 RingCT/type: yes/0
Extra: 013224021e0a7a2f8fd2819929d80045fd701dbf0a33662fb4d32c279ee55ed33c02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7af8138949c1dc5ee6cfc5f726a59da768caad703b6283439ad8be3d042b9e47 0.600000000000 1501401 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": 1032954, "vin": [ { "gen": { "height": 1032944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7af8138949c1dc5ee6cfc5f726a59da768caad703b6283439ad8be3d042b9e47" } } ], "extra": [ 1, 50, 36, 2, 30, 10, 122, 47, 143, 210, 129, 153, 41, 216, 0, 69, 253, 112, 29, 191, 10, 51, 102, 47, 180, 211, 44, 39, 158, 229, 94, 211, 60, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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