Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eced113a74200aaa714c09172653007026e20909336a3bbe30ac7a8d0cbbda0

Tx prefix hash: a77641ee71ba28ea84a944b940e008f4637101c169484b1dba00a08fa5878122
Tx public key: 1a3d0e6142cde51626a1cc02fc693c5be8f883f3fc57d1be50b097c23de07c1e
Timestamp: 1788516444 Timestamp [UTC]: 2026-09-04 10:07:24 Age [y:d:h:m:s]: 00:076:13:55:03
Block: 1627938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 54313 RingCT/type: yes/0
Extra: 011a3d0e6142cde51626a1cc02fc693c5be8f883f3fc57d1be50b097c23de07c1e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a5d0cde02c3c31c692481cf1c249d1df6a063832179afe904c24df023ffe6d4e 0.000600000000 2117958 of 15 <d7>

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": 1627948, "vin": [ { "gen": { "height": 1627938 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a5d0cde02c3c31c692481cf1c249d1df6a063832179afe904c24df023ffe6d4e", "view_tag": "d7" } } } ], "extra": [ 1, 26, 61, 14, 97, 66, 205, 229, 22, 38, 161, 204, 2, 252, 105, 60, 91, 232, 248, 131, 243, 252, 87, 209, 190, 80, 176, 151, 194, 61, 224, 124, 30 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: