Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033121bb8c04a5c5c849f49f8d104ada44e21d883c487ef4a5498b5ec418529e

Tx prefix hash: d8d6937e091a4f494a2778bc3dee2363eeac7180885f8ca78aa445e34a6842e5
Tx public key: 057d2b5057f5b0ec20c2613f7654ffbb04a4f8e88cb625c5df72ccbd002d1f51
Timestamp: 1747020711 Timestamp [UTC]: 2025-05-12 03:31:51 Age [y:d:h:m:s]: 01:194:19:28:28
Block: 1281033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403117 RingCT/type: yes/0
Extra: 01057d2b5057f5b0ec20c2613f7654ffbb04a4f8e88cb625c5df72ccbd002d1f510211000000029f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a49f0ed10041603997ba50e205e9ff353e2b71bde65598ebbb8de639b7a79d5b 0.000600000000 1768428 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": 1281043, "vin": [ { "gen": { "height": 1281033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a49f0ed10041603997ba50e205e9ff353e2b71bde65598ebbb8de639b7a79d5b" } } ], "extra": [ 1, 5, 125, 43, 80, 87, 245, 176, 236, 32, 194, 97, 63, 118, 84, 255, 187, 4, 164, 248, 232, 140, 182, 37, 197, 223, 114, 204, 189, 0, 45, 31, 81, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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: