Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 496140c10e31dbeeaa6398040a9e9957fc7d169e526a6c4ec3587875f35efeba

Tx prefix hash: 237ba0ce7da641f5924f71247316c418ed6d60c810da836f2caf31fdd770f271
Tx public key: ae7cac10dcebb72f549beea9bafb0f858506080329ccfbbbeae1ae332d50a065
Timestamp: 1722027065 Timestamp [UCT]: 2024-07-26 20:51:05 Age [y:d:h:m:s]: 00:248:12:46:26
Block: 1074350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177533 RingCT/type: yes/0
Extra: 01ae7cac10dcebb72f549beea9bafb0f858506080329ccfbbbeae1ae332d50a06502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d01e570e37d472efd6a5e20a1ac2b9bc00a9a3c2df5342ff896aaab7378da828 0.600000000000 1546863 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": 1074360, "vin": [ { "gen": { "height": 1074350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d01e570e37d472efd6a5e20a1ac2b9bc00a9a3c2df5342ff896aaab7378da828" } } ], "extra": [ 1, 174, 124, 172, 16, 220, 235, 183, 47, 84, 155, 238, 169, 186, 251, 15, 133, 133, 6, 8, 3, 41, 204, 251, 187, 234, 225, 174, 51, 45, 80, 160, 101, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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