Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed62aedf4d07853af72aaa5e134ffc20a4f1f27cdf5407d54333ee94fc49185

Tx prefix hash: 33030f954554e5e5d5362cdf2e7c972cc6523d7585b5c91ee7f9176a77d651e9
Tx public key: fc84bc99c40b87a993d939dbf4663bfb2f82dbcab3c3ea8b3e6fc3825c4224a8
Timestamp: 1749898444 Timestamp [UCT]: 2025-06-14 10:54:04 Age [y:d:h:m:s]: 00:159:11:06:13
Block: 1304792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111726 RingCT/type: yes/0
Extra: 01fc84bc99c40b87a993d939dbf4663bfb2f82dbcab3c3ea8b3e6fc3825c4224a802110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6e50c903dc140052d6aedd48f31f3865cb4680fed720c808564e86ac4022fb4 0.600000000000 1792385 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": 1304802, "vin": [ { "gen": { "height": 1304792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6e50c903dc140052d6aedd48f31f3865cb4680fed720c808564e86ac4022fb4" } } ], "extra": [ 1, 252, 132, 188, 153, 196, 11, 135, 169, 147, 217, 57, 219, 244, 102, 59, 251, 47, 130, 219, 202, 179, 195, 234, 139, 62, 111, 195, 130, 92, 66, 36, 168, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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