Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fba8c92b29d4d81fb006c9d7555fe0ce60bd59a64f6defa3cdc8a7634f24a60

Tx prefix hash: 45fcecc758d359a2efda28b2133cc7ee83d867c41f48ce91af9b5573c6a3174b
Tx public key: f4336364501ee9a0f45c7ee761ee2fe41827d0548fe1c9cd6377b0920aec451c
Timestamp: 1742646614 Timestamp [UTC]: 2025-03-22 12:30:14 Age [y:d:h:m:s]: 01:243:20:10:35
Block: 1244831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438459 RingCT/type: yes/0
Extra: 01f4336364501ee9a0f45c7ee761ee2fe41827d0548fe1c9cd6377b0920aec451c021100000005ca0c97f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 61e8869ac846a90fb633b89a5e40f144ce5a00b17cefa6b5837017025a0687ab 0.000600000000 1731822 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": 1244841, "vin": [ { "gen": { "height": 1244831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61e8869ac846a90fb633b89a5e40f144ce5a00b17cefa6b5837017025a0687ab" } } ], "extra": [ 1, 244, 51, 99, 100, 80, 30, 233, 160, 244, 92, 126, 231, 97, 238, 47, 228, 24, 39, 208, 84, 143, 225, 201, 205, 99, 119, 176, 146, 10, 236, 69, 28, 2, 17, 0, 0, 0, 5, 202, 12, 151, 245, 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: