← previous blocknext block →recent activity
Analyzing
Block #87,410,382
12 transactions · 10 stateful · 2026-07-13 04:11:39 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,410,382 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac388ba5…a800
0x34b655…2a6f
4 touches
1 conflict
0x77a99df7…d784
0x851145…3f07
4 touches
1 conflict
0xd69f26b4…c204
0x2a68ba…90c5
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0acd3db8…10a7
0x34b655…2a6f
2 touches
0 conflicts
0x0b88e8b5…76e1
0x34b655…2a6f
2 touches
0 conflicts
0x0b88e8b5…76e2
0x34b655…2a6f
2 touches
0 conflicts
0x0b88e8b5…76e6
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 0xac388ba59a…0fa800
Audit this contract →
← previous block·next block →recent activity