Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39a921c4e579bff78388dc37732bbe1089fd3b2bf2d9f55f6a7ca78912d6ee39

Tx prefix hash: a7317612aeb08ee354989ca233ecc9b1d71b1dda7103d7b1f3794210f1777dee
Tx public key: 3e2b3985caede48f014f9f47a4e45e199f1ea0a53ee6fd66274cbe113f56894c
Timestamp: 1755885832 Timestamp [UCT]: 2025-08-22 18:03:52 Age [y:d:h:m:s]: 00:044:01:22:11
Block: 1352143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31361 RingCT/type: yes/0
Extra: 013e2b3985caede48f014f9f47a4e45e199f1ea0a53ee6fd66274cbe113f56894c0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d8b52c76f7cf5669a789ce9ce3eaa6379aed5b7ba2143ad6d5f8064f013d1c 0.600000000000 1840106 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": 1352153, "vin": [ { "gen": { "height": 1352143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d8b52c76f7cf5669a789ce9ce3eaa6379aed5b7ba2143ad6d5f8064f013d1c" } } ], "extra": [ 1, 62, 43, 57, 133, 202, 237, 228, 143, 1, 79, 159, 71, 164, 228, 94, 25, 159, 30, 160, 165, 62, 230, 253, 102, 39, 76, 190, 17, 63, 86, 137, 76, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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