← previous blocknext block →recent activity
Analyzing
Block #87,352,420
13 transactions · 13 stateful · 2026-07-12 21:43:55 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,352,420 · 13 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
1w02w16w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x816c7d6d…98eb
0x34b655…2a6f
4 touches
1 conflict
0xd5a7d0e8…3462
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0463db49…5d05
0x34b655…2a6f
4 touches
1 conflict
0x0c9eb6ea…7c39
0x34b655…2a6f
4 touches
1 conflict
0xa0a5bed4…1d15
0x34b655…2a6f
4 touches
1 conflict
0x365b60bf…1c23
0x34b655…2a6f
4 touches
1 conflict
0x471515c5…322a
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
1 conflict on slot 0x816c7d6de3…ac98eb
Audit this contract →
← previous block·next block →recent activity