← previous blocknext block →recent activity
Analyzing
Block #86,314,061
30 transactions · 26 stateful · 2026-07-08 02:01:18 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,314,061 · 30 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
2w03w14w26w07w011w114w016w320w021w125w226w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x31616f97…1acc
0x34b655…2a6f
8 touches
6 conflicts
0x0ad4dbe8…ae93
0x34b655…2a6f
6 touches
3 conflicts
0x59dbc306…f976
0x34b655…2a6f
6 touches
3 conflicts
0x96047c45…b64a
0x34b655…2a6f
6 touches
3 conflicts
0xa321461b…36cf
0x34b655…2a6f
6 touches
3 conflicts
0xd800e635…b1d7
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity