Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37d93bd16d264ef6be4ebf4b1ac90906b7ed23e5c19f45fc55ab1b602aa8ea98

Tx prefix hash: 4a9346e0e784d99b447284f792a84de5c745a72c0f821c1c81ccdce7fbfc5be7
Tx public key: 88482284d400b144c6d4d770a17ae0c557bb08ce3a08ae7df569c012c97068d5
Timestamp: 1764983405 Timestamp [UTC]: 2025-12-06 01:10:05 Age [y:d:h:m:s]: 00:344:12:02:03
Block: 1427349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251568 RingCT/type: yes/0
Extra: 0188482284d400b144c6d4d770a17ae0c557bb08ce3a08ae7df569c012c97068d5021100000001fb8fd089000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0b0e21c5a6473de3186d5244194d079ba8a34fbd746111fe4bb0d82f8ac31d1d 0.000600000000 1916050 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": 1427359, "vin": [ { "gen": { "height": 1427349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b0e21c5a6473de3186d5244194d079ba8a34fbd746111fe4bb0d82f8ac31d1d" } } ], "extra": [ 1, 136, 72, 34, 132, 212, 0, 177, 68, 198, 212, 215, 112, 161, 122, 224, 197, 87, 187, 8, 206, 58, 8, 174, 125, 245, 105, 192, 18, 201, 112, 104, 213, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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: