← previous blocknext block →recent activity
Analyzing
Block #87,793,073
22 transactions · 20 stateful · 2026-07-14 22:51:55 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,793,073 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w09w110w213w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
12 touches
15 conflicts
0x28c62bca…b746
0x34b655…2a6f
8 touches
6 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x84d74093…7808
0x34b655…2a6f
8 touches
6 conflicts
0x936fd1bd…2e89
0x34b655…2a6f
8 touches
6 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 touches
6 conflicts
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
15 conflicts on slot 0x9465204cd8…debf37
Audit this contract →
← previous block·next block →recent activity