← previous blocknext block →recent activity
Analyzing
Block #85,837,424
12 transactions · 12 stateful · 2026-07-05 21:00:30 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,837,424 · 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
1w02w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e4b5149…c444
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x43aede37…4fb3
0x065c9d…c394
2 touches
0 conflicts
0x53201a46…19d1
0x065c9d…c394
2 touches
0 conflicts
0x63eec40e…b8f7
0x065c9d…c394
2 touches
0 conflicts
0x71d34cdf…03aa
0x065c9d…c394
2 touches
0 conflicts
0x721b5d14…be88
0x065c9d…c394
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 0x7e4b51491a…71c444
Audit this contract →
← previous block·next block →recent activity