Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51ce51d9a4c141d9dcb4e927df65c927df3a5eb3fff2300ce029ac1fe6d893cd

Tx prefix hash: d5a654c95004da17f0a9f22558cc287754c2dbdaa0f35562c1a7dbd829fd10f1
Tx public key: 8a95d4c405c8f09a438fe1006652b927bd06e879d83e4ca44c127398cd47c08b
Timestamp: 1773972238 Timestamp [UTC]: 2026-03-20 02:03:58 Age [y:d:h:m:s]: 00:240:12:50:30
Block: 1501605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177359 RingCT/type: yes/0
Extra: 018a95d4c405c8f09a438fe1006652b927bd06e879d83e4ca44c127398cd47c08b021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e914aaa5a2b8cf8a215101a4b4d6e68e3b51efe79d86b6f1d68bc6137bdec848 0.000600000000 1991289 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": 1501615, "vin": [ { "gen": { "height": 1501605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e914aaa5a2b8cf8a215101a4b4d6e68e3b51efe79d86b6f1d68bc6137bdec848" } } ], "extra": [ 1, 138, 149, 212, 196, 5, 200, 240, 154, 67, 143, 225, 0, 102, 82, 185, 39, 189, 6, 232, 121, 216, 62, 76, 164, 76, 18, 115, 152, 205, 71, 192, 139, 2, 17, 0, 0, 0, 5, 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: