Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3b5ac0bb20f3b4c5a858eb16f142482913edbebeb242d83af32389871cf0d27

Tx prefix hash: 3e0296b94e7c1bdb8c0969572fbeb9adaad351a793299f6525ddd4ca9e45fdd5
Tx public key: 02a4316727cdafd2e83fcd39e52a2d2eca2c46928e61e5d6433cc5ff0b62bf65
Timestamp: 1774374782 Timestamp [UTC]: 2026-03-24 17:53:02 Age [y:d:h:m:s]: 00:241:16:24:21
Block: 1504933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178414 RingCT/type: yes/0
Extra: 0102a4316727cdafd2e83fcd39e52a2d2eca2c46928e61e5d6433cc5ff0b62bf65021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 28b5147a037cf84cf364a2bc600a36b7ef3fbdba53cfd5f532bdb0cbc52d0745 0.000600000000 1994661 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": 1504943, "vin": [ { "gen": { "height": 1504933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b5147a037cf84cf364a2bc600a36b7ef3fbdba53cfd5f532bdb0cbc52d0745" } } ], "extra": [ 1, 2, 164, 49, 103, 39, 205, 175, 210, 232, 63, 205, 57, 229, 42, 45, 46, 202, 44, 70, 146, 142, 97, 229, 214, 67, 60, 197, 255, 11, 98, 191, 101, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: