← previous blocknext block →recent activity
Analyzing
Block #87,331,453
40 transactions · 31 stateful · 2026-07-12 19:23:45 UTC
Parallelism
90/100
Blocked
39%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,331,453 · 40 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
2w04w16w17w09w010w113w118w022w023w124w225w327w228w229w332w036w139w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x15336fe3…1f37
0x34b655…2a6f
4 touches
1 conflict
0x1db39d01…fbf5
0x34b655…2a6f
4 touches
1 conflict
0x8eef368f…aa21
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x40e2d65d…2a35
0x3bd359…433a
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity