Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fae669bdaceb9e86a69ec4afd5bce47365cdb9f3d6fbfe7b571f39cc78363818

Tx prefix hash: cf350651584249726b01c0d496cbf1f25a365cae9304d5d7d1c0d127bece3871
Tx public key: 712a1c9fde06e8f817800205df4370cc1d7dd29fdc6370b4a76ecbe09797fda3
Timestamp: 1773895298 Timestamp [UTC]: 2026-03-19 04:41:38 Age [y:d:h:m:s]: 00:240:18:35:44
Block: 1500970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177502 RingCT/type: yes/0
Extra: 01712a1c9fde06e8f817800205df4370cc1d7dd29fdc6370b4a76ecbe09797fda302110000000bf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e0d3d7f2bc7c93d8e7292a6b0344bc636293a6158e16704891fd27cf6de34b0c 0.000600000000 1990648 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": 1500980, "vin": [ { "gen": { "height": 1500970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0d3d7f2bc7c93d8e7292a6b0344bc636293a6158e16704891fd27cf6de34b0c" } } ], "extra": [ 1, 113, 42, 28, 159, 222, 6, 232, 248, 23, 128, 2, 5, 223, 67, 112, 204, 29, 125, 210, 159, 220, 99, 112, 180, 167, 110, 203, 224, 151, 151, 253, 163, 2, 17, 0, 0, 0, 11, 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: