Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a57006eb35f874aa56a48c62855f422acb9844db189be3ae5dfac9fb33a8408

Tx prefix hash: b71c69b1b230aafede93ee3fd2647115da3198cc92006c63d437e6c3f76a77c4
Tx public key: 3dd440b14145ba35153d0d611d2a9b09bafaeb5698dc8a79a21174dcf1b8f8f1
Timestamp: 1733971530 Timestamp [UCT]: 2024-12-12 02:45:30 Age [y:d:h:m:s]: 01:005:02:43:37
Block: 1173294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262062 RingCT/type: yes/0
Extra: 013dd440b14145ba35153d0d611d2a9b09bafaeb5698dc8a79a21174dcf1b8f8f1021100000001c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02d5a36fe5afef8f641dc9055cd730b97575de20bd7429fba65e9a945d93762e 0.600000000000 1659301 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": 1173304, "vin": [ { "gen": { "height": 1173294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02d5a36fe5afef8f641dc9055cd730b97575de20bd7429fba65e9a945d93762e" } } ], "extra": [ 1, 61, 212, 64, 177, 65, 69, 186, 53, 21, 61, 13, 97, 29, 42, 155, 9, 186, 250, 235, 86, 152, 220, 138, 121, 162, 17, 116, 220, 241, 184, 248, 241, 2, 17, 0, 0, 0, 1, 199, 202, 20, 193, 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