← previous blocknext block →recent activity
Analyzing
Block #96,092,204
14 transactions · 14 stateful · 2026-08-15 03:08:31 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,092,204 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w08w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e6f835b…f889
0x968279…9342
4 touches
1 conflict
0x0a76d782…183d
0x968279…9342
4 touches
1 conflict
0x3e6f835b…f882
0x968279…9342
4 touches
1 conflict
0x3e6f835b…f883
0x968279…9342
4 touches
1 conflict
0x3e6f835b…f886
0x968279…9342
4 touches
1 conflict
0x3e6f835b…f887
0x968279…9342
4 touches
1 conflict
0x0463db49…5d05
0x34b655…2a6f
4 touches
1 conflict
0x177d036a…1c5d
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: 0x96827978…f09342
1 conflict on slot 0x3e6f835bce…30f889
Audit this contract →
← previous block·next block →recent activity