← previous blocknext block →recent activity
Analyzing
Block #96,075,833
15 transactions · 13 stateful · 2026-08-15 01:46:11 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,075,833 · 15 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
5w06w07w18w09w111w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0efa563…24d8
0x968279…9342
4 touches
1 conflict
0xa0efa563…24db
0x968279…9342
4 touches
1 conflict
0xa0efa563…24dc
0x968279…9342
4 touches
1 conflict
0xa0efa563…24dd
0x968279…9342
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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 0xa0efa5632c…fe24d8
Audit this contract →
← previous block·next block →recent activity