Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf575ee93e1cd4c687d866b25bb3bebbfda05d9a9cf62d08dced35b68e596dee

Tx prefix hash: 9941788cb0e90fb1a8eb69fd22c683c0b3dbb747cd2cb7c8550e56cb15226161
Tx public key: 53dcfff9dd6f346425c59a88e36b4b28f31ec5292b0e8dea085040cfe4e2e47c
Timestamp: 1773686060 Timestamp [UTC]: 2026-03-16 18:34:20 Age [y:d:h:m:s]: 00:251:02:25:06
Block: 1499263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184887 RingCT/type: yes/0
Extra: 0153dcfff9dd6f346425c59a88e36b4b28f31ec5292b0e8dea085040cfe4e2e47c021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d11b3200f460ac3d2fcd2b8f436423a83e5e238b267697a4ae79c808fc88a3a0 0.000600000000 1988917 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": 1499273, "vin": [ { "gen": { "height": 1499263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d11b3200f460ac3d2fcd2b8f436423a83e5e238b267697a4ae79c808fc88a3a0" } } ], "extra": [ 1, 83, 220, 255, 249, 221, 111, 52, 100, 37, 197, 154, 136, 227, 107, 75, 40, 243, 30, 197, 41, 43, 14, 141, 234, 8, 80, 64, 207, 228, 226, 228, 124, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: