Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b627ba75b220e448760269081d798732f6fb531846d3ef8c03d07bc272a92b9

Tx prefix hash: 3470f12e481b5c862322aab5acd78000fbd90ae6cbdb797a0a241d702a073b2c
Tx public key: fb0c5f1dd926323e51c0ab278bc5181f03d1eb53755bf2dcccb81b2374bdd9c1
Timestamp: 1706826725 Timestamp [UCT]: 2024-02-01 22:32:05 Age [y:d:h:m:s]: 01:100:05:09:52
Block: 948334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332707 RingCT/type: yes/0
Extra: 01fb0c5f1dd926323e51c0ab278bc5181f03d1eb53755bf2dcccb81b2374bdd9c10211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 349d49d4f8671a3149219aec105c2c4aebdbf70801f73d90e862665d8138b998 0.600000000000 1406718 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": 948344, "vin": [ { "gen": { "height": 948334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "349d49d4f8671a3149219aec105c2c4aebdbf70801f73d90e862665d8138b998" } } ], "extra": [ 1, 251, 12, 95, 29, 217, 38, 50, 62, 81, 192, 171, 39, 139, 197, 24, 31, 3, 209, 235, 83, 117, 91, 242, 220, 204, 184, 27, 35, 116, 189, 217, 193, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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