Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9c012f9a2dcccd7c262e49ef315c28ca17dcebe083fa870614f6e528aabc85

Tx prefix hash: f4bb3ce282059012d4463a364c31c018c6fa9a873d922f078b35ee1663ac4a6a
Tx public key: 1a36ab46d745f37257407c87bac5b0b825ebeff872c5c92b8a8356a1a12fea87
Timestamp: 1772214243 Timestamp [UTC]: 2026-02-27 17:44:03 Age [y:d:h:m:s]: 00:260:13:18:20
Block: 1487064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191654 RingCT/type: yes/0
Extra: 011a36ab46d745f37257407c87bac5b0b825ebeff872c5c92b8a8356a1a12fea87021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b55cf5707324f7c0576412e7eace32b863f5c5e94bd1785fd2b1c181ccc075e0 0.000600000000 1976526 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": 1487074, "vin": [ { "gen": { "height": 1487064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b55cf5707324f7c0576412e7eace32b863f5c5e94bd1785fd2b1c181ccc075e0" } } ], "extra": [ 1, 26, 54, 171, 70, 215, 69, 243, 114, 87, 64, 124, 135, 186, 197, 176, 184, 37, 235, 239, 248, 114, 197, 201, 43, 138, 131, 86, 161, 161, 47, 234, 135, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: