Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab275f8313079bebf8aa9e9fb29e57aab2afeed947b6bca4d7d64cd1e16f14ad

Tx prefix hash: e10db614abf8ed3b2535fbe82be248c1493629bfc2dbfd26c136b6ce980288a0
Tx public key: 58208eb4f1c448ce06f86537624518ec65575fa93160f32a9aec5f1dc0eb3ea1
Timestamp: 1743989285 Timestamp [UTC]: 2025-04-07 01:28:05 Age [y:d:h:m:s]: 01:222:01:45:15
Block: 1255928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422668 RingCT/type: yes/0
Extra: 0158208eb4f1c448ce06f86537624518ec65575fa93160f32a9aec5f1dc0eb3ea1021100000004dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 78d65fdf0750f1e243850c25c820fec22a3aad046725c4852ae446c4878e97b0 0.000600000000 1743035 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": 1255938, "vin": [ { "gen": { "height": 1255928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78d65fdf0750f1e243850c25c820fec22a3aad046725c4852ae446c4878e97b0" } } ], "extra": [ 1, 88, 32, 142, 180, 241, 196, 72, 206, 6, 248, 101, 55, 98, 69, 24, 236, 101, 87, 95, 169, 49, 96, 243, 42, 154, 236, 95, 29, 192, 235, 62, 161, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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: