Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b678d5c32fdea44452989f9ce2cd07dad9dc97b716ecc8b3d0dfe48fc7d88f0

Tx prefix hash: c319ec5b2dd37b9eb8e23bfead7ef6bc2a97e31ddf74da09c10aad1e3484d160
Tx public key: a18f6eb3c3128a193df4d3832c201d18eb77b7e8402c2913181597c36c04066b
Timestamp: 1774346308 Timestamp [UTC]: 2026-03-24 09:58:28 Age [y:d:h:m:s]: 00:237:12:07:46
Block: 1504706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175243 RingCT/type: yes/0
Extra: 01a18f6eb3c3128a193df4d3832c201d18eb77b7e8402c2913181597c36c04066b021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 956b691c78ae43b4f1c6f698681470c0d768e86415a37551ca8ac816326c1f8e 0.000600000000 1994432 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": 1504716, "vin": [ { "gen": { "height": 1504706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "956b691c78ae43b4f1c6f698681470c0d768e86415a37551ca8ac816326c1f8e" } } ], "extra": [ 1, 161, 143, 110, 179, 195, 18, 138, 25, 61, 244, 211, 131, 44, 32, 29, 24, 235, 119, 183, 232, 64, 44, 41, 19, 24, 21, 151, 195, 108, 4, 6, 107, 2, 17, 0, 0, 0, 5, 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: