← previous blocknext block →recent activity
Analyzing
Block #86,045,836
30 transactions · 23 stateful · 2026-07-06 20:10:53 UTC
Parallelism
87/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,045,836 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
13w014w116w122w023w126w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3923d7de…bb41
0x754704…b603
4 touches
1 conflict
0x504ac60b…20a6
0x754704…b603
4 touches
1 conflict
0x527f20e3…82e7
0x754704…b603
4 touches
1 conflict
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0x81955a0a…29ee
0x6657d1…8ccc
4 touches
1 conflict
0xeeb8b7fc…24d6
0x6657d1…8ccc
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity