Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1426cca6b530fb0e26edf1ee4507a0a2a862c781fd0e01fb8cf2e019ecae76b0

Tx prefix hash: 620c1d688afba5c008151cd0ee04b3e6ad8c820cba20b3bbe09060a037a69afa
Tx public key: 1f2fdaaab55f2a46d20d88d370cb80af8d3a348e9e46b894a248b082160db0ed
Timestamp: 1747829353 Timestamp [UTC]: 2025-05-21 12:09:13 Age [y:d:h:m:s]: 00:361:18:49:47
Block: 1287751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248734 RingCT/type: yes/0
Extra: 011f2fdaaab55f2a46d20d88d370cb80af8d3a348e9e46b894a248b082160db0ed0211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3aed1746bb8cac702563d416a2f1c3b76e2876d468529cf91a6fc4e9f65d2c31 0.000600000000 1775218 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": 1287761, "vin": [ { "gen": { "height": 1287751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aed1746bb8cac702563d416a2f1c3b76e2876d468529cf91a6fc4e9f65d2c31" } } ], "extra": [ 1, 31, 47, 218, 170, 181, 95, 42, 70, 210, 13, 136, 211, 112, 203, 128, 175, 141, 58, 52, 142, 158, 70, 184, 148, 162, 72, 176, 130, 22, 13, 176, 237, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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: