Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f125c8f5bd13aacc607b324d65a719a6cf62a7c45b159cebf3226a8611745d

Tx prefix hash: 5bd7e9e20bb28c059703ae2e3a691fb6ef4160f2bec46fae04077e8fce5b502a
Tx public key: 8bca504c3d2f414c078e350175552c3db4fbbad5315f6747a9fe72b6e464eb4b
Timestamp: 1748411452 Timestamp [UTC]: 2025-05-28 05:50:52 Age [y:d:h:m:s]: 01:174:21:37:40
Block: 1292563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389040 RingCT/type: yes/0
Extra: 018bca504c3d2f414c078e350175552c3db4fbbad5315f6747a9fe72b6e464eb4b02110000000d523560da000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d65e12d9f9c6017512152bd2adac6b4fac7242623b44272abcc29fdf21e1a24a 0.000600000000 1780034 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": 1292573, "vin": [ { "gen": { "height": 1292563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d65e12d9f9c6017512152bd2adac6b4fac7242623b44272abcc29fdf21e1a24a" } } ], "extra": [ 1, 139, 202, 80, 76, 61, 47, 65, 76, 7, 142, 53, 1, 117, 85, 44, 61, 180, 251, 186, 213, 49, 95, 103, 71, 169, 254, 114, 182, 228, 100, 235, 75, 2, 17, 0, 0, 0, 13, 82, 53, 96, 218, 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: