Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0bd3770ad4470c15fdad0fa8b69bda30622b98950ddeb6e1cc4906b262dc0e6

Tx prefix hash: 19c1b10caf9d70e9ad879f20770ad4985b0e244be522e40344dd4701844b3be1
Tx public key: db6e4809a6fbf0fadc32c925a7ef9f7c236ad53a3e9f795f17204134e3ff7416
Timestamp: 1708768630 Timestamp [UCT]: 2024-02-24 09:57:10 Age [y:d:h:m:s]: 01:052:22:05:44
Block: 964450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298835 RingCT/type: yes/0
Extra: 01db6e4809a6fbf0fadc32c925a7ef9f7c236ad53a3e9f795f17204134e3ff741602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 555a7249f64cd8419e4b98d33f3f6a54459aa60875b7ab340f52b484b5cfb711 0.600000000000 1424189 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": 964460, "vin": [ { "gen": { "height": 964450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "555a7249f64cd8419e4b98d33f3f6a54459aa60875b7ab340f52b484b5cfb711" } } ], "extra": [ 1, 219, 110, 72, 9, 166, 251, 240, 250, 220, 50, 201, 37, 167, 239, 159, 124, 35, 106, 213, 58, 62, 159, 121, 95, 23, 32, 65, 52, 227, 255, 116, 22, 2, 17, 0, 0, 0, 2, 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