Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cad2ce1d50e5cdc1fc4d5182731895c33de87ee4640566976fc169dc9fd3f356

Tx prefix hash: e4a30d506604fd8ebb797dcbdd4d3b26a5f4393438730ac5253ba2c047ce1383
Tx public key: 039f432437fe0a4abdcffbc57e50fec81dde04b61ff4d260781e27143cab1d4c
Timestamp: 1728259481 Timestamp [UTC]: 2024-10-07 00:04:41 Age [y:d:h:m:s]: 02:046:21:42:42
Block: 1126031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558119 RingCT/type: yes/0
Extra: 01039f432437fe0a4abdcffbc57e50fec81dde04b61ff4d260781e27143cab1d4c02110000000491e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0571e04ec047d272cf8ae51f03da1531dc713f1246ce796669583e0f5d4c73eb 0.000600000000 1608804 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": 1126041, "vin": [ { "gen": { "height": 1126031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0571e04ec047d272cf8ae51f03da1531dc713f1246ce796669583e0f5d4c73eb" } } ], "extra": [ 1, 3, 159, 67, 36, 55, 254, 10, 74, 189, 207, 251, 197, 126, 80, 254, 200, 29, 222, 4, 182, 31, 244, 210, 96, 120, 30, 39, 20, 60, 171, 29, 76, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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: