Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed8c27c48608e87227e83c4f8a19cceef099b0241679840a183b5fca0d1a2bcd

Tx prefix hash: 386bee4139d20c332345f15bd42abda1741f7fa4291c8766feb7a5ea6e4efbea
Tx public key: d3b499b5a31c67d37eaa129ee8eb6a6fce1691915d3c181953fb5c1c4f186bc0
Timestamp: 1764249731 Timestamp [UTC]: 2025-11-27 13:22:11 Age [y:d:h:m:s]: 00:353:18:55:35
Block: 1421279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258239 RingCT/type: yes/0
Extra: 01d3b499b5a31c67d37eaa129ee8eb6a6fce1691915d3c181953fb5c1c4f186bc0021100000216d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b25b0f454b38d89da7885d04c8d75312455614bac1708d7e62aac96a8179b083 0.000600000000 1909836 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": 1421289, "vin": [ { "gen": { "height": 1421279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b25b0f454b38d89da7885d04c8d75312455614bac1708d7e62aac96a8179b083" } } ], "extra": [ 1, 211, 180, 153, 181, 163, 28, 103, 211, 126, 170, 18, 158, 232, 235, 106, 111, 206, 22, 145, 145, 93, 60, 24, 25, 83, 251, 92, 28, 79, 24, 107, 192, 2, 17, 0, 0, 2, 22, 214, 225, 157, 124, 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: