Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef8267a2b1d594710005f392670455aaee2b1baff8d08a329c36ef6aae92f852

Tx prefix hash: 7bdff468474fde3062dd52dc400e086bc8671c36dbcdae1814f106b943109b00
Tx public key: 4a5cd414213aed9e4e473e5b8fc5d9777493ebe809a59dc9b1bf6da77c105776
Timestamp: 1711823130 Timestamp [UCT]: 2024-03-30 18:25:30 Age [y:d:h:m:s]: 01:009:20:18:33
Block: 989788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267979 RingCT/type: yes/0
Extra: 014a5cd414213aed9e4e473e5b8fc5d9777493ebe809a59dc9b1bf6da77c1057760211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4758860729aa4a6dc1f5ade9ed861f088e467f55b63a5da7dc818f5cfdc20421 0.600000000000 1450106 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": 989798, "vin": [ { "gen": { "height": 989788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4758860729aa4a6dc1f5ade9ed861f088e467f55b63a5da7dc818f5cfdc20421" } } ], "extra": [ 1, 74, 92, 212, 20, 33, 58, 237, 158, 78, 71, 62, 91, 143, 197, 217, 119, 116, 147, 235, 232, 9, 165, 157, 201, 177, 191, 109, 167, 124, 16, 87, 118, 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