Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fafe3b274e253d5f4d3f8afda22bf1121ef2aa0fee76636b30403fa8f52a2bd6

Tx prefix hash: c7e5a936b19141d30d9aa242257172352efd5efae360283ad806c0bbc3228c5e
Tx public key: a99327b3d627963130e6cb110445f9cdaffbb63f08b357a4d5d951a018d1609e
Timestamp: 1763318044 Timestamp [UCT]: 2025-11-16 18:34:04 Age [y:d:h:m:s]: 00:040:18:55:36
Block: 1413554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29205 RingCT/type: yes/0
Extra: 01a99327b3d627963130e6cb110445f9cdaffbb63f08b357a4d5d951a018d1609e02110000000243b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e49334f14ce6ea5642558d82b8a96a601fe7954d83ad63cd7f3f15acc56696f 0.600000000000 1902033 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 dinasty-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": 1413564, "vin": [ { "gen": { "height": 1413554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e49334f14ce6ea5642558d82b8a96a601fe7954d83ad63cd7f3f15acc56696f" } } ], "extra": [ 1, 169, 147, 39, 179, 214, 39, 150, 49, 48, 230, 203, 17, 4, 69, 249, 205, 175, 251, 182, 63, 8, 179, 87, 164, 213, 217, 81, 160, 24, 209, 96, 158, 2, 17, 0, 0, 0, 2, 67, 181, 4, 113, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8