← previous blocknext block →recent activity
Analyzing
Block #87,503,746
27 transactions · 22 stateful · 2026-07-13 14:35:57 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,503,746 · 27 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
2w03w14w05w17w017w118w219w020w321w422w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a38e46…a68c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc9377f93…3739
0x34b655…2a6f
6 touches
3 conflicts
0xf12ab614…ea6e
0x34b655…2a6f
6 touches
3 conflicts
0xfb53ecf8…bd11
0x34b655…2a6f
6 touches
3 conflicts
0x3e950538…2259
0x34b655…2a6f
4 touches
1 conflict
0x41d9a134…ccfe
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 0xe5a38e469a…0da68c
Audit this contract →
← previous block·next block →recent activity