← previous blocknext block →recent activity
Analyzing
Block #85,714,131
12 transactions · 12 stateful · 2026-07-05 07:19:40 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,714,131 · 12 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
4w05w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6cdad76f…2bed
0x34b655…2a6f
4 touches
1 conflict
0xfdde6236…b2a5
0x34b655…2a6f
4 touches
1 conflict
0x0a4a1be4…71be
0x34b655…2a6f
4 touches
1 conflict
0x298a7547…5fb1
0x065c9d…c394
2 touches
0 conflicts
0xc1d575a2…7430
0x065c9d…c394
2 touches
0 conflicts
0xefb673ff…92cd
0x065c9d…c394
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity