Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ff1308fbe83d08236a732d96e701992c05a8002bb9e967e6c5ed027183a8e3b

Tx prefix hash: 904f5719cedc5b84f45926b2b9400eff1a45e13d3b525f0e5b0b455818d4e5d1
Tx public key: 450bc96395b43e358363773ad2700304a5bb36ebdc0cd3249f31cdc8920df040
Timestamp: 1756096097 Timestamp [UTC]: 2025-08-25 04:28:17 Age [y:d:h:m:s]: 00:260:10:14:10
Block: 1353888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178283 RingCT/type: yes/0
Extra: 01450bc96395b43e358363773ad2700304a5bb36ebdc0cd3249f31cdc8920df0400211000000042609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ddf8ffdf27c14b2ccf58685723049dce5fda28fb8f50eed858a50e0d1e7279d2 0.000600000000 1841867 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": 1353898, "vin": [ { "gen": { "height": 1353888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf8ffdf27c14b2ccf58685723049dce5fda28fb8f50eed858a50e0d1e7279d2" } } ], "extra": [ 1, 69, 11, 201, 99, 149, 180, 62, 53, 131, 99, 119, 58, 210, 112, 3, 4, 165, 187, 54, 235, 220, 12, 211, 36, 159, 49, 205, 200, 146, 13, 240, 64, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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: