← previous blocknext block →recent activity
Analyzing
Block #87,581,018
17 transactions · 11 stateful · 2026-07-13 23:13:32 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,581,018 · 17 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
1w02w03w17w09w211w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fb86cd0…c67b
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x91889d52…f2fa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67c
0x34b655…2a6f
4 touches
1 conflict
0xe8705a56…b335
0x34b655…2a6f
4 touches
1 conflict
0xf345ee5f…bf84
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x4fb86cd027…a5c67b
Audit this contract →
← previous block·next block →recent activity