← previous blocknext block →recent activity
Analyzing
Block #95,202,831
14 transactions · 12 stateful · 2026-08-12 00:20:02 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,202,831 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w28w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6e37efb…afc2
0xe52b14…7230
6 touches
3 conflicts
0xa6e37efb…afc0
0xe52b14…7230
6 touches
3 conflicts
0xa5bf91eb…0b03
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x51232c8c…f30e
0xe52b14…7230
6 touches
3 conflicts
0x51232c8c…f30c
0xe52b14…7230
6 touches
3 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xe52b1424…bb7230
3 conflicts on slot 0xa6e37efb84…caafc2
Audit this contract →
← previous block·next block →recent activity