← previous blocknext block →recent activity
Analyzing
Block #86,075,781
20 transactions · 16 stateful · 2026-07-06 23:30:33 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,075,781 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w113w014w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb82d6699…c0c1
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xc9bf65ef…12ff
0xd32edf…ff58
3 touches
1 conflict
0x1a004c59…980f
0x188d58…ea8e
2 touches
0 conflicts
0x1a004c59…9810
0x188d58…ea8e
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 0xb82d66991e…49c0c1
Audit this contract →
← previous block·next block →recent activity