← previous blocknext block →recent activity
Analyzing
Block #86,237,815
17 transactions · 14 stateful · 2026-07-07 17:32:09 UTC
Parallelism
76/100
Blocked
21%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,237,815 · 17 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
6w07w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x207cc41e…57c6
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0xbd9491f7…dd92
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe52da074…4dc0
0x34b655…2a6f
4 touches
1 conflict
0xc13fcfc8…2598
0x065c9d…c394
2 touches
0 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
1 conflict on slot 0x207cc41ebf…5057c6
Audit this contract →
← previous block·next block →recent activity