← previous blocknext block →recent activity
Analyzing
Block #88,077,427
17 transactions · 15 stateful · 2026-07-16 06:33:48 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,077,427 · 17 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
2w04w05w16w07w110w111w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5777bd87…71bd
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x8eb21bd9…aa8b
0x34b655…2a6f
6 touches
3 conflicts
0x57e95ab1…d5ef
0x34b655…2a6f
6 touches
3 conflicts
0x74e46435…fdcd
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x5777bd874f…7071bd
Audit this contract →
← previous block·next block →recent activity