Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 402657edabb337e7a03836fa8cf19fabf1a9905bc7f709d636cbb8b38efe4a14

Tx prefix hash: 25bdcae56ba1b97b3b024e0f8db19f3a1c7de00ba7b9a291d66b46711d614f20
Tx public key: 806c228d0ae3a5f9e3f89d7120050f7a84e09ce9a763571ce210521239a7d149
Timestamp: 1742091173 Timestamp [UTC]: 2025-03-16 02:12:53 Age [y:d:h:m:s]: 01:250:16:28:58
Block: 1240247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443247 RingCT/type: yes/0
Extra: 01806c228d0ae3a5f9e3f89d7120050f7a84e09ce9a763571ce210521239a7d1490211000000061f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 843004ec8d0b2432f99a3fdd66ec35e42c973d38e2ec853b190f268ae80e0cb8 0.000600000000 1727212 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": 1240257, "vin": [ { "gen": { "height": 1240247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "843004ec8d0b2432f99a3fdd66ec35e42c973d38e2ec853b190f268ae80e0cb8" } } ], "extra": [ 1, 128, 108, 34, 141, 10, 227, 165, 249, 227, 248, 157, 113, 32, 5, 15, 122, 132, 224, 156, 233, 167, 99, 87, 28, 226, 16, 82, 18, 57, 167, 209, 73, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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: