Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5365fe5443b91d9a6ec1c33bc64cdc326c5eaad67a603ee1f0ab2bbfc346c367

Tx prefix hash: 701f041b9fa68be1b13eea149e7a8d6702f07e991337d4f65d5847c22afe2b32
Tx public key: e5a6fffa864d3ba77503900518d5a7d3d3b7f8c90afcddc0020d69d6b4038ba0
Timestamp: 1762384838 Timestamp [UCT]: 2025-11-05 23:20:38 Age [y:d:h:m:s]: 00:047:17:02:33
Block: 1405806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34165 RingCT/type: yes/0
Extra: 01e5a6fffa864d3ba77503900518d5a7d3d3b7f8c90afcddc0020d69d6b4038ba00211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ef4ab9781c813d76e72213af21da3b11bc1feb7f435fafd6a6549b389cc4f62 0.600000000000 1894187 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": 1405816, "vin": [ { "gen": { "height": 1405806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ef4ab9781c813d76e72213af21da3b11bc1feb7f435fafd6a6549b389cc4f62" } } ], "extra": [ 1, 229, 166, 255, 250, 134, 77, 59, 167, 117, 3, 144, 5, 24, 213, 167, 211, 211, 183, 248, 201, 10, 252, 221, 192, 2, 13, 105, 214, 180, 3, 139, 160, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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