Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ccad044b2c7e31c4170810841f3aba22f14827c0ea3ba819224864fb6385b8d

Tx prefix hash: 1b2a6a00881024432975fcd861757ab37d47fbf164e2aeab2d131f12c3147069
Tx public key: e51dfb45df39f00ef21559ce8545120626f8c516e8aec321a5dd187b83accc13
Timestamp: 1741957024 Timestamp [UTC]: 2025-03-14 12:57:04 Age [y:d:h:m:s]: 01:074:21:37:58
Block: 1239139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306115 RingCT/type: yes/0
Extra: 01e51dfb45df39f00ef21559ce8545120626f8c516e8aec321a5dd187b83accc130211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d4da7fd4703693fae91738bd789c224ad05cc6e18701f0b23b8b3a5c4df60d3c 0.000600000000 1726104 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 dinastycoin-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": 1239149, "vin": [ { "gen": { "height": 1239139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4da7fd4703693fae91738bd789c224ad05cc6e18701f0b23b8b3a5c4df60d3c" } } ], "extra": [ 1, 229, 29, 251, 69, 223, 57, 240, 14, 242, 21, 89, 206, 133, 69, 18, 6, 38, 248, 197, 22, 232, 174, 195, 33, 165, 221, 24, 123, 131, 172, 204, 19, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: