Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db53e7b5f0ae54580e4107da07e24fad1928d831da61cee0c9cf38d70d94cd6c

Tx prefix hash: 14ad67bfd557a382b098f14fcc7b59a0be35909d417ec0d9c887b79dc468edee
Tx public key: 6fafc0aa2fa7225781cad2cfdfcef045d8eabb87b58c16a1d3fc098e652f5d6e
Timestamp: 1740370148 Timestamp [UTC]: 2025-02-24 04:09:08 Age [y:d:h:m:s]: 01:266:09:36:09
Block: 1225960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454453 RingCT/type: yes/0
Extra: 016fafc0aa2fa7225781cad2cfdfcef045d8eabb87b58c16a1d3fc098e652f5d6e021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fee4fec5c13d8530c8a6e7cdd3af405d1459a5715e22926c8d320e8a1bcc479a 0.000600000000 1712831 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": 1225970, "vin": [ { "gen": { "height": 1225960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fee4fec5c13d8530c8a6e7cdd3af405d1459a5715e22926c8d320e8a1bcc479a" } } ], "extra": [ 1, 111, 175, 192, 170, 47, 167, 34, 87, 129, 202, 210, 207, 223, 206, 240, 69, 216, 234, 187, 135, 181, 140, 22, 161, 211, 252, 9, 142, 101, 47, 93, 110, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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: