← previous blocknext block →recent activity
Analyzing
Block #86,448,936
24 transactions · 18 stateful · 2026-07-08 17:02:19 UTC
Parallelism
92/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,448,936 · 24 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
2w03w15w011w012w116w017w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd526c4bd…dbf2
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x7ab120ed…0ff4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8388eab6…83ff
0x34b655…2a6f
4 touches
1 conflict
0xcfe06a18…b5b5
0x69df8a…6292
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 0xd526c4bd25…59dbf2
Audit this contract →
← previous block·next block →recent activity