← previous blocknext block →recent activity
Analyzing
Block #96,084,942
16 transactions · 14 stateful · 2026-08-15 02:32:00 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,084,942 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w08w49w512w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x34b222ef…4afc
0x34b655…2a6f
6 touches
3 conflicts
0x69d5a813…e035
0x34b655…2a6f
6 touches
3 conflicts
0x981b7617…6093
0x34b655…2a6f
4 touches
1 conflict
0x87d62b39…b5ab
0x34b655…2a6f
4 touches
1 conflict
0x4ecb58c4…ac20
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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: Perpl
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity