Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5dc2db4d49576c1904b65cf6cec2d4c9e05d67e6caeff7706b14ac66b6f50c0

Tx prefix hash: 68629daf74f9cbe0621c757e2085035ec4d8e84f6eaef92396bad3bef17f2506
Tx public key: 0ff97632942006a77f812ac32e980cf557eb2b9d05ad740448d3004d4ddd68a1
Timestamp: 1759273460 Timestamp [UTC]: 2025-09-30 23:04:20 Age [y:d:h:m:s]: 01:044:08:40:02
Block: 1380032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297957 RingCT/type: yes/0
Extra: 010ff97632942006a77f812ac32e980cf557eb2b9d05ad740448d3004d4ddd68a1021100000001a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e5f2cd07ce866105425edcf04dc853e1ffdc58e5992e151fab8e9c8b4e80b0b4 0.000600000000 1868143 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": 1380042, "vin": [ { "gen": { "height": 1380032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5f2cd07ce866105425edcf04dc853e1ffdc58e5992e151fab8e9c8b4e80b0b4" } } ], "extra": [ 1, 15, 249, 118, 50, 148, 32, 6, 167, 127, 129, 42, 195, 46, 152, 12, 245, 87, 235, 43, 157, 5, 173, 116, 4, 72, 211, 0, 77, 77, 221, 104, 161, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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: