Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04bb007b24c2e37d5319764a8d7a7cc4c0b6867da0fd8c0217c345047a48705a

Tx prefix hash: 27fb0fdedd125beb3715718080c4a496335150709c36980cde4ab50ca1620169
Tx public key: cf214c78bf95d9180365288c59ebb4d9d20e06d4650198d60a2c7d26fd1674a4
Timestamp: 1755461075 Timestamp [UTC]: 2025-08-17 20:04:35 Age [y:d:h:m:s]: 00:274:10:36:15
Block: 1348722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189347 RingCT/type: yes/0
Extra: 01cf214c78bf95d9180365288c59ebb4d9d20e06d4650198d60a2c7d26fd1674a402110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 71f07a3dbae94e042ddb91d264ba7d68dcd2ef6b32c8212c254a17770a0dd2cf 0.000600000000 1836651 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": 1348732, "vin": [ { "gen": { "height": 1348722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71f07a3dbae94e042ddb91d264ba7d68dcd2ef6b32c8212c254a17770a0dd2cf" } } ], "extra": [ 1, 207, 33, 76, 120, 191, 149, 217, 24, 3, 101, 40, 140, 89, 235, 180, 217, 210, 14, 6, 212, 101, 1, 152, 214, 10, 44, 125, 38, 253, 22, 116, 164, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: