Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74480e126c41193391b22b5264a0ce853147972dcc081d1673be4a175afe11ba

Tx prefix hash: 39d7238fa94eb8538e60f92d020cfacf0b1ea0f224907eb86dda4a1c85e05ebd
Tx public key: b10bdecef089b4cb857d7035b512ade0ff24b614d35a7cf198d3fd37482b1d8d
Timestamp: 1732696522 Timestamp [UCT]: 2024-11-27 08:35:22 Age [y:d:h:m:s]: 00:349:12:10:28
Block: 1162721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247322 RingCT/type: yes/0
Extra: 01b10bdecef089b4cb857d7035b512ade0ff24b614d35a7cf198d3fd37482b1d8d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1765ddee15dc983d41874fa817c312dae38daee7dd0469afdf01601fd9e0d9cf 0.600000000000 1648378 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": 1162731, "vin": [ { "gen": { "height": 1162721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1765ddee15dc983d41874fa817c312dae38daee7dd0469afdf01601fd9e0d9cf" } } ], "extra": [ 1, 177, 11, 222, 206, 240, 137, 180, 203, 133, 125, 112, 53, 181, 18, 173, 224, 255, 36, 182, 20, 211, 90, 124, 241, 152, 211, 253, 55, 72, 43, 29, 141, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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