Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa5fae6ec8bf9d8e4911f9260ca980bc4ad54c929b9cb66e5692198df377abc6

Tx prefix hash: 8aaa7a2448cf4e145640efdc6e88b618596dc281ef7d3f998043a28884c4657f
Tx public key: a7e26f4c8d8dcd800c94c59ca7a5a8fe06c7039b94c41b99143917ab2b9fd318
Timestamp: 1746425072 Timestamp [UTC]: 2025-05-05 06:04:32 Age [y:d:h:m:s]: 01:200:14:46:08
Block: 1276104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407390 RingCT/type: yes/0
Extra: 01a7e26f4c8d8dcd800c94c59ca7a5a8fe06c7039b94c41b99143917ab2b9fd3180211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4cd6f535dcb674dfd9bb4dbd2673055819682c080744d6e4e44815275baa034a 0.000600000000 1763427 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": 1276114, "vin": [ { "gen": { "height": 1276104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cd6f535dcb674dfd9bb4dbd2673055819682c080744d6e4e44815275baa034a" } } ], "extra": [ 1, 167, 226, 111, 76, 141, 141, 205, 128, 12, 148, 197, 156, 167, 165, 168, 254, 6, 199, 3, 155, 148, 196, 27, 153, 20, 57, 23, 171, 43, 159, 211, 24, 2, 17, 0, 0, 0, 1, 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: