← previous blocknext block →recent activity
Analyzing
Block #96,568,373
10 transactions · 8 stateful · 2026-08-16 19:03:47 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,568,373 · 10 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
3w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad52adf2…0dd2
0x34b655…2a6f
4 touches
1 conflict
0xeeb46b9e…93e1
0x34b655…2a6f
4 touches
1 conflict
0x58d6b9cf…7c9e
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x0ae0abcd…7a14
0x34b655…2a6f
2 touches
0 conflicts
0x0d3522bc…cd3b
0x34b655…2a6f
2 touches
0 conflicts
0x18f24f0d…9f83
0x34b655…2a6f
2 touches
0 conflicts
0x36ce0155…1682
0x34b655…2a6f
2 touches
0 conflicts
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: Perpl
1 conflict on slot 0xad52adf293…b70dd2
Audit this contract →
← previous block·next block →recent activity