Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94e3d2c7664bef7512a9ea4e0a4f28156d8c3f3c4983acbd84680771e0d58766

Tx prefix hash: a3dfa2dd5f27e8af42a4930be4471fb3d14cffc59c6af72809b0aa0efb69447e
Tx public key: 8067051082d11a9becc586b0c431f2f2d3191ae051bb0c247dc46371b47b3a6b
Timestamp: 1702758520 Timestamp [UCT]: 2023-12-16 20:28:40 Age [y:d:h:m:s]: 01:112:09:21:57
Block: 914622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341437 RingCT/type: yes/0
Extra: 018067051082d11a9becc586b0c431f2f2d3191ae051bb0c247dc46371b47b3a6b02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16e4f2cd8ee3c4a9ad34de5ff68cd843ca2d918a5a2e5cc335e09ec7e76dbdfe 0.600000000000 1371972 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": 914632, "vin": [ { "gen": { "height": 914622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16e4f2cd8ee3c4a9ad34de5ff68cd843ca2d918a5a2e5cc335e09ec7e76dbdfe" } } ], "extra": [ 1, 128, 103, 5, 16, 130, 209, 26, 155, 236, 197, 134, 176, 196, 49, 242, 242, 211, 25, 26, 224, 81, 187, 12, 36, 125, 196, 99, 113, 180, 123, 58, 107, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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