← previous blocknext block →recent activity
Analyzing
Block #86,168,769
12 transactions · 11 stateful · 2026-07-07 09:51:06 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,168,769 · 12 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
1w02w15w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc4cb048e…7562
0x34b655…2a6f
4 touches
1 conflict
0x951e19e4…1234
0xd32edf…ff58
3 touches
1 conflict
0x39bce8d2…ae94
0x065c9d…c394
2 touches
0 conflicts
0xad44fffc…9225
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0xf6b83261…584a
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity