← previous blocknext block →recent activity
Analyzing
Block #87,616,795
20 transactions · 13 stateful · 2026-07-14 03:12:48 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,616,795 · 20 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
1w02w16w09w110w212w214w317w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca3f1796…927c
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0xa562e808…4bde
0x34b655…2a6f
6 touches
3 conflicts
0xf4ca4a80…b15d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb4e0c126…218f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
6 conflicts on slot 0xca3f1796b4…ff927c
Audit this contract →
← previous block·next block →recent activity