Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b06f86775aebedfb35b59ab3dcd419a76b2ba3af75fe86fb098efc32ac5610a9

Tx prefix hash: 7e3b048ea5b9847a35496a2acbeb9307f972d52002dac4ee847b5ff8507ca6ee
Tx public key: 307773b395455016d34e20d88b492fc93c74e89fb2fb0d84aac4b35623697716
Timestamp: 1720637644 Timestamp [UCT]: 2024-07-10 18:54:04 Age [y:d:h:m:s]: 00:136:23:43:44
Block: 1062847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98022 RingCT/type: yes/0
Extra: 01307773b395455016d34e20d88b492fc93c74e89fb2fb0d84aac4b35623697716021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7aedff80a5b428fd5ba8c081fbe0e7b252210d605145ed51a495570778cf8c7 0.600000000000 1533358 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": 1062857, "vin": [ { "gen": { "height": 1062847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7aedff80a5b428fd5ba8c081fbe0e7b252210d605145ed51a495570778cf8c7" } } ], "extra": [ 1, 48, 119, 115, 179, 149, 69, 80, 22, 211, 78, 32, 216, 139, 73, 47, 201, 60, 116, 232, 159, 178, 251, 13, 132, 170, 196, 179, 86, 35, 105, 119, 22, 2, 17, 0, 0, 0, 4, 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