Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e26edbf16e740bc1e546ff3deb996085e06af5c32a519ffa39115fb4103edb

Tx prefix hash: dd8aea0b5ab7f05890d478811f79eafa7b8ba7ed289b6278ff7442a71e7285de
Tx public key: 8fd5a257e30ac178f05308f71f7d861e2271f1ce5805a3cc3bc65f93799afb9d
Timestamp: 1773821965 Timestamp [UTC]: 2026-03-18 08:19:25 Age [y:d:h:m:s]: 00:242:00:12:57
Block: 1500361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178412 RingCT/type: yes/0
Extra: 018fd5a257e30ac178f05308f71f7d861e2271f1ce5805a3cc3bc65f93799afb9d021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1fef11f01b2446a19a51e2a3ca4cdcdbaf9b049d67599a89410320e292b5e588 0.000600000000 1990031 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": 1500371, "vin": [ { "gen": { "height": 1500361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fef11f01b2446a19a51e2a3ca4cdcdbaf9b049d67599a89410320e292b5e588" } } ], "extra": [ 1, 143, 213, 162, 87, 227, 10, 193, 120, 240, 83, 8, 247, 31, 125, 134, 30, 34, 113, 241, 206, 88, 5, 163, 204, 59, 198, 95, 147, 121, 154, 251, 157, 2, 17, 0, 0, 0, 3, 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: