Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8da9ddbc96ce2200e5d6a894f0d79f3f03828d95626fb1182af5957f3b87a15f

Tx prefix hash: cc64dd4ada9444d99f97c59fdcf651aeee6210c9bdca8127773fc06beaa5d861
Tx public key: 887907e4f1ad2741e57ddefe30a7e0ebcec1dcfeaa8ce4c44ff9ce85be78450f
Timestamp: 1713285072 Timestamp [UCT]: 2024-04-16 16:31:12 Age [y:d:h:m:s]: 01:002:18:48:33
Block: 1001867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262949 RingCT/type: yes/0
Extra: 01887907e4f1ad2741e57ddefe30a7e0ebcec1dcfeaa8ce4c44ff9ce85be78450f0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f97cd6ba9627fce99d8bb72dbb037a873642b81a69775b849ab4255d0d60f7bd 0.600000000000 1462379 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": 1001877, "vin": [ { "gen": { "height": 1001867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f97cd6ba9627fce99d8bb72dbb037a873642b81a69775b849ab4255d0d60f7bd" } } ], "extra": [ 1, 136, 121, 7, 228, 241, 173, 39, 65, 229, 125, 222, 254, 48, 167, 224, 235, 206, 193, 220, 254, 170, 140, 228, 196, 79, 249, 206, 133, 190, 120, 69, 15, 2, 17, 0, 0, 0, 5, 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