Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9b2bb54ad5c35967b11cf6c8489365fcda8dfd6f256e7f8e7eba3c5a897b9c8

Tx prefix hash: 69d95da119a7e7304ee92a2e7b5b9faa16b2f87dd0a68be57f984ddd3e977a96
Tx public key: 3dc9c17b35433b222cfa792b9da4755c8ef30639a38853d616a346e905e78435
Timestamp: 1742601156 Timestamp [UTC]: 2025-03-21 23:52:36 Age [y:d:h:m:s]: 01:219:15:39:09
Block: 1244449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419386 RingCT/type: yes/0
Extra: 013dc9c17b35433b222cfa792b9da4755c8ef30639a38853d616a346e905e78435021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3a7fc442f0326d03ad677d3d4ea42a248247ea82621ee7e69e9c11a372769b4f 0.000600000000 1731440 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": 1244459, "vin": [ { "gen": { "height": 1244449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a7fc442f0326d03ad677d3d4ea42a248247ea82621ee7e69e9c11a372769b4f" } } ], "extra": [ 1, 61, 201, 193, 123, 53, 67, 59, 34, 44, 250, 121, 43, 157, 164, 117, 92, 142, 243, 6, 57, 163, 136, 83, 214, 22, 163, 70, 233, 5, 231, 132, 53, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: