Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4284957e84edc0af9c952d4335699d07c8391c153e8349b101253dfcd5c27368

Tx prefix hash: a940e7bb03774ed8b170941c27bd32dd8410a37f420341eae1076afc44bf7603
Tx public key: 5b430c4fdcec17fb50d87ceb2b09d33df03a09838d38d7bf5f084e4aafdaf260
Timestamp: 1710424647 Timestamp [UCT]: 2024-03-14 13:57:27 Age [y:d:h:m:s]: 01:247:06:58:22
Block: 978192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435434 RingCT/type: yes/0
Extra: 015b430c4fdcec17fb50d87ceb2b09d33df03a09838d38d7bf5f084e4aafdaf26002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a37de27670636ad77c1b51816434abc178c5b565988fcea30bf6a6ee4f3da9a2 0.600000000000 1438211 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": 978202, "vin": [ { "gen": { "height": 978192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a37de27670636ad77c1b51816434abc178c5b565988fcea30bf6a6ee4f3da9a2" } } ], "extra": [ 1, 91, 67, 12, 79, 220, 236, 23, 251, 80, 216, 124, 235, 43, 9, 211, 61, 240, 58, 9, 131, 141, 56, 215, 191, 95, 8, 78, 74, 175, 218, 242, 96, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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