Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96567066c0b0157483f73f7d222db75d1d68afd70b1b992c14cb1d7ae8d500d8

Tx prefix hash: 766b1974076e6c2b6ff7db17dfa2bc9a95548cc7623875adc60c8caa0565c31a
Tx public key: 6ed8b2e3ef4aaf9c4bb934abcb668b4fbd17c6cd8aff5fdf5b12fb2fbdde3338
Timestamp: 1703889902 Timestamp [UCT]: 2023-12-29 22:45:02 Age [y:d:h:m:s]: 01:137:10:39:25
Block: 923986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359374 RingCT/type: yes/0
Extra: 016ed8b2e3ef4aaf9c4bb934abcb668b4fbd17c6cd8aff5fdf5b12fb2fbdde33380211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c6b4720695fe4457fab1e53240cac82416bc3c48a7dc5559efd0d62e6a0cf9a 0.600000000000 1381728 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": 923996, "vin": [ { "gen": { "height": 923986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c6b4720695fe4457fab1e53240cac82416bc3c48a7dc5559efd0d62e6a0cf9a" } } ], "extra": [ 1, 110, 216, 178, 227, 239, 74, 175, 156, 75, 185, 52, 171, 203, 102, 139, 79, 189, 23, 198, 205, 138, 255, 95, 223, 91, 18, 251, 47, 189, 222, 51, 56, 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