← previous blocknext block →recent activity
Analyzing
Block #87,713,561
19 transactions · 18 stateful · 2026-07-14 13:59:51 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,713,561 · 19 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
3w04w05w16w07w18w29w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x0f8965bb…e238
0x34b655…2a6f
4 touches
1 conflict
0x181ad9cf…26f4
0x34b655…2a6f
4 touches
1 conflict
0x244fd0dc…ddcc
0x34b655…2a6f
4 touches
1 conflict
0x33708be5…6990
0x34b655…2a6f
4 touches
1 conflict
0x3f68590d…2a18
0x34b655…2a6f
4 touches
1 conflict
0x767799cd…f423
0xc8689a…ee79
4 touches
1 conflict
0xd0f6f4f2…dffa
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity