Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f20b9897332a6527e70b8d2efa8f3a5dee34420a593672cac47b4762c4e8ac2d

Tx prefix hash: 72bc5e487071d6a0f6ef656ab182dd2eba959119ebd6c1fc9c1d1797514f659e
Tx public key: b26e9f4966c7776b61d7f0ac38698f171d29be7f2a5fba3007994ae33292d494
Timestamp: 1771882643 Timestamp [UTC]: 2026-02-23 21:37:23 Age [y:d:h:m:s]: 00:264:00:20:30
Block: 1484339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194090 RingCT/type: yes/0
Extra: 01b26e9f4966c7776b61d7f0ac38698f171d29be7f2a5fba3007994ae33292d494021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2d041bd84c666ee56762a1de3491a88e1d316068d52a44cb3ca90d681f64a0cb 0.000600000000 1973759 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": 1484349, "vin": [ { "gen": { "height": 1484339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d041bd84c666ee56762a1de3491a88e1d316068d52a44cb3ca90d681f64a0cb" } } ], "extra": [ 1, 178, 110, 159, 73, 102, 199, 119, 107, 97, 215, 240, 172, 56, 105, 143, 23, 29, 41, 190, 127, 42, 95, 186, 48, 7, 153, 74, 227, 50, 146, 212, 148, 2, 17, 0, 0, 0, 6, 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: