Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ec81c8d4b0d00e5cf86f82a2446d51698c32f4154765c4f9bb93c6d5d6e9bbc

Tx prefix hash: 518e4f0d559d487a144f494e9f95388b5037d40ce87626ff730e91869eefa86f
Tx public key: 39215075b2bcaa0a72633f16e8a59db70e1ccfa65e5a343473813f2692e62f5d
Timestamp: 1789168486 Timestamp [UTC]: 2026-09-11 23:14:46 Age [y:d:h:m:s]: 00:064:20:24:05
Block: 1633403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 45711 RingCT/type: yes/0
Extra: 0139215075b2bcaa0a72633f16e8a59db70e1ccfa65e5a343473813f2692e62f5d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 70905d8ff985156164b7505cf8ccd96a8cfdc5f14ffe8e6be501ba9ea12f7942 0.000600000000 2123433 of 15 <b1>

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": 1633413, "vin": [ { "gen": { "height": 1633403 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "70905d8ff985156164b7505cf8ccd96a8cfdc5f14ffe8e6be501ba9ea12f7942", "view_tag": "b1" } } } ], "extra": [ 1, 57, 33, 80, 117, 178, 188, 170, 10, 114, 99, 63, 22, 232, 165, 157, 183, 14, 28, 207, 166, 94, 90, 52, 52, 115, 129, 63, 38, 146, 230, 47, 93 ], "rct_signatures": { "type": 0 } }


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