Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cddd9433c540cc1d5b4bb2d9f8d3551282227bbf8e5b8f28793d09badfc1771e

Tx prefix hash: 358baf98c7f2f6bda3971cbd7527e265d32d522ab650ae42663452e84bd20f61
Tx public key: be5a6b5f41f946f81ecc2ca89d7da2349e9a1b99cf197ad24292c9d91c6de938
Timestamp: 1757829877 Timestamp [UTC]: 2025-09-14 06:04:37 Age [y:d:h:m:s]: 01:066:17:40:53
Block: 1368064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314179 RingCT/type: yes/0
Extra: 01be5a6b5f41f946f81ecc2ca89d7da2349e9a1b99cf197ad24292c9d91c6de938021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 67266401427ea1aec21bb9669fca859602eb0eb80f801a6b422ac46912834ab9 0.000600000000 1856103 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": 1368074, "vin": [ { "gen": { "height": 1368064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67266401427ea1aec21bb9669fca859602eb0eb80f801a6b422ac46912834ab9" } } ], "extra": [ 1, 190, 90, 107, 95, 65, 249, 70, 248, 30, 204, 44, 168, 157, 125, 162, 52, 158, 154, 27, 153, 207, 25, 122, 210, 66, 146, 201, 217, 28, 109, 233, 56, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: