Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5777db42f86515c8788c4c33f40cfc6e0e31c3ce444b113881f2de30d30aa90

Tx prefix hash: 5a59669f042d9a9fe36067e1d889369e2e9369ab2412445ef98637420845c541
Tx public key: f843e1c93fc188f58863edb9d458dcb61d86e8efc9fcf9ebabaebac66e7fb58a
Timestamp: 1759764078 Timestamp [UCT]: 2025-10-06 15:21:18 Age [y:d:h:m:s]: 00:118:23:10:09
Block: 1384101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85011 RingCT/type: yes/0
Extra: 01f843e1c93fc188f58863edb9d458dcb61d86e8efc9fcf9ebabaebac66e7fb58a021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e36478b3afc2ce163fd869286b9949fe344914a5b1aa1c4e45c5411c2e558d6 0.600000000000 1872250 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": 1384111, "vin": [ { "gen": { "height": 1384101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e36478b3afc2ce163fd869286b9949fe344914a5b1aa1c4e45c5411c2e558d6" } } ], "extra": [ 1, 248, 67, 225, 201, 63, 193, 136, 245, 136, 99, 237, 185, 212, 88, 220, 182, 29, 134, 232, 239, 201, 252, 249, 235, 171, 174, 186, 198, 110, 127, 181, 138, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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