Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f0ae0b3ecfc9535302f6cc8f1826d3b80ad7d44db9d99b23d7fe987253ea43

Tx prefix hash: 2b0e27d935c13588613db34b656865ebaeeea36ee9693b8b42ea5e0a653093fd
Tx public key: 4fe8b0ec8036f39370426e5130c14c976d4064b60d898068bb1c3b92a48b27d8
Timestamp: 1769464203 Timestamp [UTC]: 2026-01-26 21:50:03 Age [y:d:h:m:s]: 00:294:09:59:03
Block: 1464313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215924 RingCT/type: yes/0
Extra: 014fe8b0ec8036f39370426e5130c14c976d4064b60d898068bb1c3b92a48b27d8021100000006215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0db44e9404611a68ad56eb752d4b4ddcf86d88c62eae1191513d8b41820b27f4 0.000600000000 1953539 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": 1464323, "vin": [ { "gen": { "height": 1464313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db44e9404611a68ad56eb752d4b4ddcf86d88c62eae1191513d8b41820b27f4" } } ], "extra": [ 1, 79, 232, 176, 236, 128, 54, 243, 147, 112, 66, 110, 81, 48, 193, 76, 151, 109, 64, 100, 182, 13, 137, 128, 104, 187, 28, 59, 146, 164, 139, 39, 216, 2, 17, 0, 0, 0, 6, 33, 91, 191, 137, 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: