← previous blocknext block →recent activity
Analyzing
Block #85,345,157
16 transactions · 16 stateful · 2026-07-03 14:21:22 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,345,157 · 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
2w07w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa20a130c…5d59
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
6 touches
3 conflicts
0xe10dad88…8549
0x34b655…2a6f
6 touches
3 conflicts
0xbf077403…b465
0x34b655…2a6f
6 touches
3 conflicts
0x8c660fa7…127a
0x34b655…2a6f
4 touches
1 conflict
0x06c59b8c…89c0
0x34b655…2a6f
4 touches
1 conflict
0x076e4b80…4d01
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 0xa20a130ca6…b85d59
Audit this contract →
← previous block·next block →recent activity