Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e22ca51c1e6f0429cf4e697abce974ee105b638367d9d7760d342fb45d37f4a

Tx prefix hash: b8ae6aa17f6a3cceb52fc1c09eeb4da8ce1c34441055f5c936bf91062f2c9089
Tx public key: 6396881c33e12f727f4255e8bc563b783e7dc2470128cdddb21548a4333781ba
Timestamp: 1743904605 Timestamp [UTC]: 2025-04-06 01:56:45 Age [y:d:h:m:s]: 01:223:14:58:17
Block: 1255240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423789 RingCT/type: yes/0
Extra: 016396881c33e12f727f4255e8bc563b783e7dc2470128cdddb21548a4333781ba0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3988db787ced96c51766f5a2daca75c1ca7576281037bfb09e7a65adcbede2c8 0.000600000000 1742343 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": 1255250, "vin": [ { "gen": { "height": 1255240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3988db787ced96c51766f5a2daca75c1ca7576281037bfb09e7a65adcbede2c8" } } ], "extra": [ 1, 99, 150, 136, 28, 51, 225, 47, 114, 127, 66, 85, 232, 188, 86, 59, 120, 62, 125, 194, 71, 1, 40, 205, 221, 178, 21, 72, 164, 51, 55, 129, 186, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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: