← previous blocknext block →recent activity
Analyzing
Block #87,513,819
14 transactions · 13 stateful · 2026-07-13 15:43:23 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,513,819 · 14 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
1w02w14w15w210w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0x59037442…7fd5
0x34b655…2a6f
8 touches
6 conflicts
0xda192fb4…0911
0x34b655…2a6f
6 touches
3 conflicts
0x13c5b486…d41e
0x34b655…2a6f
6 touches
3 conflicts
0x1d73754c…2e95
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2ae834f7…a036
0x34b655…2a6f
6 touches
3 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity