Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7ba3c62d6f546561575f18a8a22be2b5a447cec5a22f0ad4e07d1ce5497614

Tx prefix hash: 26b853c32fbe1d0940443c06c6ff5a285e3842fcedfed9f87de24d8bc723eb81
Tx public key: 2c11c8df4aa57385c852d44160d5c81d12a627acd5f68a78d07496801dd52117
Timestamp: 1747682452 Timestamp [UTC]: 2025-05-19 19:20:52 Age [y:d:h:m:s]: 01:178:02:11:31
Block: 1286518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391154 RingCT/type: yes/0
Extra: 012c11c8df4aa57385c852d44160d5c81d12a627acd5f68a78d07496801dd521170211000000069f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a237517ee8fede10b1903a5feda285eaa501bbad8a9ec9dd6e4af4d1362e814d 0.000600000000 1773983 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": 1286528, "vin": [ { "gen": { "height": 1286518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a237517ee8fede10b1903a5feda285eaa501bbad8a9ec9dd6e4af4d1362e814d" } } ], "extra": [ 1, 44, 17, 200, 223, 74, 165, 115, 133, 200, 82, 212, 65, 96, 213, 200, 29, 18, 166, 39, 172, 213, 246, 138, 120, 208, 116, 150, 128, 29, 213, 33, 23, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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: