← previous blocknext block →recent activity
Analyzing
Block #86,250,424
19 transactions · 18 stateful · 2026-07-07 18:56:29 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,250,424 · 19 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
2w03w04w113w115w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0x9b4939c0…02c8
0x34b655…2a6f
4 touches
1 conflict
0xb1053b93…3963
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xd93edb3f…94ec
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity