Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 208e994f12c8e495280ffb468aaf664f52adb6ab5854653b08616404390b2a92

Tx prefix hash: 84fc7c12e37d0c432dea06472c206bbd3590b27ddaf720e0d136d0a715ab5b62
Tx public key: 773fd7c55d2d4db370e9e85cc36cb4935b2c7ec852dac2f359a4a6ecfa6372bb
Timestamp: 1723505246 Timestamp [UCT]: 2024-08-12 23:27:26 Age [y:d:h:m:s]: 00:307:12:58:56
Block: 1086615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219613 RingCT/type: yes/0
Extra: 01773fd7c55d2d4db370e9e85cc36cb4935b2c7ec852dac2f359a4a6ecfa6372bb021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9484b02e4f3d262d8ed0b3a6ee57ea9f17974a319e1c00f922497dc4e56a8c2 0.600000000000 1561212 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": 1086625, "vin": [ { "gen": { "height": 1086615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9484b02e4f3d262d8ed0b3a6ee57ea9f17974a319e1c00f922497dc4e56a8c2" } } ], "extra": [ 1, 119, 63, 215, 197, 93, 45, 77, 179, 112, 233, 232, 92, 195, 108, 180, 147, 91, 44, 126, 200, 82, 218, 194, 243, 89, 164, 166, 236, 250, 99, 114, 187, 2, 17, 0, 0, 0, 8, 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