Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7704c54fc8a9df150887d6ed2c3500a5b0aec38feaba9a5e4ab2f7e43e9d8be

Tx prefix hash: 05f5ac7cc16fb42053e17a40ea6d70e40c9488863d9c756f0d86fb3f8ae42bc2
Tx public key: 3ac33ac9d454e40f6d8b9ea001b7fda56aac10e8ce74ee90895f8c77b4f79eab
Timestamp: 1743698817 Timestamp [UTC]: 2025-04-03 16:46:57 Age [y:d:h:m:s]: 01:096:07:10:39
Block: 1253532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324366 RingCT/type: yes/0
Extra: 013ac33ac9d454e40f6d8b9ea001b7fda56aac10e8ce74ee90895f8c77b4f79eab021100000014a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ba1bc6dde91e2a2e6760aeb110e00cc5c802bec97400a42990e259c6052c6ed5 0.000600000000 1740613 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": 1253542, "vin": [ { "gen": { "height": 1253532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba1bc6dde91e2a2e6760aeb110e00cc5c802bec97400a42990e259c6052c6ed5" } } ], "extra": [ 1, 58, 195, 58, 201, 212, 84, 228, 15, 109, 139, 158, 160, 1, 183, 253, 165, 106, 172, 16, 232, 206, 116, 238, 144, 137, 95, 140, 119, 180, 247, 158, 171, 2, 17, 0, 0, 0, 20, 162, 237, 1, 107, 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: