← previous blocknext block →recent activity
Analyzing
Block #87,362,834
9 transactions · 8 stateful · 2026-07-12 22:53:32 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,362,834 · 9 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
2w03w15w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x87f7db3b…33dc
0x34b655…2a6f
4 touches
1 conflict
0xacb691b6…8e39
0x34b655…2a6f
4 touches
1 conflict
0xd7e9e97b…8d1e
0x34b655…2a6f
4 touches
1 conflict
0x0a5529a7…492e
0x34b655…2a6f
2 touches
0 conflicts
0x0e128f00…762d
0x34b655…2a6f
2 touches
0 conflicts
0x16ba1d53…4480
0x34b655…2a6f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity