Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5667a4cd6e9cc2cbf0623ecfab143aae39bd0768b53f8ec1fe497b5d1414ba4

Tx prefix hash: 36556b7edff045d2e7b1e25832ccd212ddbd782e60a3fae9011cd5ec391d43d7
Tx public key: 2d23c32746f13ba847c5290593aa90c1e6474d75d20468cc85acd633c9cd9cce
Timestamp: 1762400587 Timestamp [UCT]: 2025-11-06 03:43:07 Age [y:d:h:m:s]: 00:060:17:20:44
Block: 1405940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43508 RingCT/type: yes/0
Extra: 012d23c32746f13ba847c5290593aa90c1e6474d75d20468cc85acd633c9cd9cce021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7058dfb6a22a4cfd342bad63650b95b0b6de8ebbae6edd0f06b5ecced8f90349 0.600000000000 1894321 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": 1405950, "vin": [ { "gen": { "height": 1405940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7058dfb6a22a4cfd342bad63650b95b0b6de8ebbae6edd0f06b5ecced8f90349" } } ], "extra": [ 1, 45, 35, 195, 39, 70, 241, 59, 168, 71, 197, 41, 5, 147, 170, 144, 193, 230, 71, 77, 117, 210, 4, 104, 204, 133, 172, 214, 51, 201, 205, 156, 206, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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