← previous blocknext block →recent activity
Analyzing
Block #88,354,892
26 transactions · 26 stateful · 2026-07-17 13:30:20 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #88,354,892 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w08w312w115w316w423w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5d2e788d…5867
0x34b655…2a6f
4 touches
1 conflict
0x6e5d7a21…b2fe
0x34b655…2a6f
4 touches
1 conflict
0x987ee7de…772f
0x34b655…2a6f
4 touches
1 conflict
0xc1e16402…a780
0x34b655…2a6f
4 touches
1 conflict
0xb64473b0…0d6f
0xc8689a…ee79
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