Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a23bbc378c2d1d187dd16a3ea7b804e9d6c99ca9b66cd9bcfc29029f3d01f9cd

Tx prefix hash: 12aaa4a7c4d8d3dceb244df3d7bb5d7f13d29fda4b3d3be65d1d503f5c798de3
Tx public key: b189edf6f8b3513d0871d86ea35e6abdb1683d2a338d3002c9ddf8ac8ed62ea1
Timestamp: 1772804334 Timestamp [UTC]: 2026-03-06 13:38:54 Age [y:d:h:m:s]: 00:257:03:41:29
Block: 1491965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189308 RingCT/type: yes/0
Extra: 01b189edf6f8b3513d0871d86ea35e6abdb1683d2a338d3002c9ddf8ac8ed62ea1021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600010000 xmr

stealth address amount amount idx tag
00: ba29e75369e23513b7e21a56f3d97ecca264c7422cc04df2dd09da6dd0b552bb 0.000600010000 1981501 of 0 -

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": 1491975, "vin": [ { "gen": { "height": 1491965 } } ], "vout": [ { "amount": 600010000, "target": { "key": "ba29e75369e23513b7e21a56f3d97ecca264c7422cc04df2dd09da6dd0b552bb" } } ], "extra": [ 1, 177, 137, 237, 246, 248, 179, 81, 61, 8, 113, 216, 110, 163, 94, 106, 189, 177, 104, 61, 42, 51, 141, 48, 2, 201, 221, 248, 172, 142, 214, 46, 161, 2, 17, 0, 0, 0, 4, 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: