Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a2e60b603fc12e374fa0799a465d4d5b8e654c12de9f8b3f34679c02bb8e346

Tx prefix hash: 34394d789ae2214acf6c6f10ae09bea4b731977541f376782f6260ad514af4d3
Tx public key: 5b718fc6f3e1da5d7ffe31f3ae920bcb022a45b9bf5718b419c79c0f75d4cdae
Timestamp: 1790459044 Timestamp [UTC]: 2026-09-26 21:44:04 Age [y:d:h:m:s]: 00:049:14:50:20
Block: 1644269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 34626 RingCT/type: yes/0
Extra: 015b718fc6f3e1da5d7ffe31f3ae920bcb022a45b9bf5718b419c79c0f75d4cdae

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e0b917edd963b769c8831a7340efa13e2aee6265ca5a9a6f1b687a10a345084c 0.000600000000 2134355 of 15 <f8>

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": 1644279, "vin": [ { "gen": { "height": 1644269 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "e0b917edd963b769c8831a7340efa13e2aee6265ca5a9a6f1b687a10a345084c", "view_tag": "f8" } } } ], "extra": [ 1, 91, 113, 143, 198, 243, 225, 218, 93, 127, 254, 49, 243, 174, 146, 11, 203, 2, 42, 69, 185, 191, 87, 24, 180, 25, 199, 156, 15, 117, 212, 205, 174 ], "rct_signatures": { "type": 0 } }


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