Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b547f41d426853e3eecdae5f02e2e3191982ee9cc8e8f05b11906b26987f361c

Tx prefix hash: 4983c45e11eeb90fd002532a383f735465b5408f2e944f7ec535aa8d988d9df5
Tx public key: 755f2c580368096ef3d519936a55eef8d63e544e5311e4addf22e1fa33064db1
Timestamp: 1749687066 Timestamp [UTC]: 2025-06-12 00:11:06 Age [y:d:h:m:s]: 00:336:09:13:05
Block: 1303091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230410 RingCT/type: yes/0
Extra: 01755f2c580368096ef3d519936a55eef8d63e544e5311e4addf22e1fa33064db1021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8dde8686b434060941e4ac0d5e64d5d94b4422647c209e420412a26a4f84e149 0.000600000000 1790666 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": 1303101, "vin": [ { "gen": { "height": 1303091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dde8686b434060941e4ac0d5e64d5d94b4422647c209e420412a26a4f84e149" } } ], "extra": [ 1, 117, 95, 44, 88, 3, 104, 9, 110, 243, 213, 25, 147, 106, 85, 238, 248, 214, 62, 84, 78, 83, 17, 228, 173, 223, 34, 225, 250, 51, 6, 77, 177, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: