← previous blocknext block →recent activity
Analyzing
Block #87,628,333
18 transactions · 16 stateful · 2026-07-14 04:29:59 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,628,333 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w111w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x6bf71f68…fd07
0x34b655…2a6f
6 touches
3 conflicts
0xef1cbbb7…8cc8
0x34b655…2a6f
6 touches
3 conflicts
0x43bc2389…898f
0x34b655…2a6f
6 touches
3 conflicts
0x978c66ea…b1ef
0x34b655…2a6f
4 touches
1 conflict
0xa5d9de4c…cb1d
0x34b655…2a6f
4 touches
1 conflict
0xc0209a91…eebf
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
3 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity