Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e63a661a0a3ce0c1b8c796909a4e47f663932e42f0e96f2f63d462c2967b278

Tx prefix hash: 4f7f7663e7d9c22578c069afbf9c4d1c6ad16e92919a286ddd5fb35694961903
Tx public key: ce9435f61c0f6040bbe4bac252a7cdf9a62526d611b0d5c8cf57a5464726f0ea
Timestamp: 1711660864 Timestamp [UCT]: 2024-03-28 21:21:04 Age [y:d:h:m:s]: 00:286:07:19:12
Block: 988434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204922 RingCT/type: yes/0
Extra: 01ce9435f61c0f6040bbe4bac252a7cdf9a62526d611b0d5c8cf57a5464726f0ea0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fe5a6f9fb3880e122a2f7f87ea952b72d5621b030f76c42f624be86390097df 0.600000000000 1448713 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": 988444, "vin": [ { "gen": { "height": 988434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fe5a6f9fb3880e122a2f7f87ea952b72d5621b030f76c42f624be86390097df" } } ], "extra": [ 1, 206, 148, 53, 246, 28, 15, 96, 64, 187, 228, 186, 194, 82, 167, 205, 249, 166, 37, 38, 214, 17, 176, 213, 200, 207, 87, 165, 70, 71, 38, 240, 234, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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