← previous blocknext block →recent activity
Analyzing
Block #86,231,202
17 transactions · 14 stateful · 2026-07-07 16:48:01 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,231,202 · 17 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
8w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x5e7da795…a150
0x34b655…2a6f
4 touches
1 conflict
0xc12a9d89…e9b6
0x34b655…2a6f
4 touches
1 conflict
0x37d710c8…45c1
0x34b655…2a6f
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x5ddc5828…3893
0x3e4f2b…ba84
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity