Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a3ce84eaa3100c9ed1bceccbe2d0db22b70175d07e1441fd06452aa6b14234

Tx prefix hash: 3fd4db43a05d796b61a9505b29c84b9852f01d5344056190e2d16d33d41b7f72
Tx public key: 5f141bd7de559d5101b4aece5729810e3b8aed4ae85f8b2627b323235d88e439
Timestamp: 1735555239 Timestamp [UCT]: 2024-12-30 10:40:39 Age [y:d:h:m:s]: 00:356:14:05:01
Block: 1186378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252425 RingCT/type: yes/0
Extra: 015f141bd7de559d5101b4aece5729810e3b8aed4ae85f8b2627b323235d88e439021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df0f80dd94a477a005da23198add690507ecbf8a905d2c3dc9f38f170b4437c0 0.600000000000 1672859 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": 1186388, "vin": [ { "gen": { "height": 1186378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df0f80dd94a477a005da23198add690507ecbf8a905d2c3dc9f38f170b4437c0" } } ], "extra": [ 1, 95, 20, 27, 215, 222, 85, 157, 81, 1, 180, 174, 206, 87, 41, 129, 14, 59, 138, 237, 74, 232, 95, 139, 38, 39, 179, 35, 35, 93, 136, 228, 57, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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