Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d53491332e943cf72ce2d7bfab7318f6dfa26e2c78581bd8c3dc71bfe093062b

Tx prefix hash: 3817e30cb4bc8819f3e65d44624195f9348c46dc62430288c6d22ecc5c61e3c8
Tx public key: bb7e427151633fd9cb4413ba6e79ab89ee4f6c40d2b61892a8fdd2bd183a604f
Timestamp: 1771144926 Timestamp [UTC]: 2026-02-15 08:42:06 Age [y:d:h:m:s]: 00:094:12:28:46
Block: 1478210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61041 RingCT/type: yes/0
Extra: 01bb7e427151633fd9cb4413ba6e79ab89ee4f6c40d2b61892a8fdd2bd183a604f021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 63d5a16784cf75529dcbc7d21760ac1aa432dc172e0d7e1981e965113243a208 0.000600000000 1967538 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": 1478220, "vin": [ { "gen": { "height": 1478210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63d5a16784cf75529dcbc7d21760ac1aa432dc172e0d7e1981e965113243a208" } } ], "extra": [ 1, 187, 126, 66, 113, 81, 99, 63, 217, 203, 68, 19, 186, 110, 121, 171, 137, 238, 79, 108, 64, 210, 182, 24, 146, 168, 253, 210, 189, 24, 58, 96, 79, 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: