← previous blocknext block →recent activity
Analyzing
Block #92,771,221
23 transactions · 23 stateful · 2026-08-03 12:10:53 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,771,221 · 23 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
2w04w05w16w27w39w112w114w316w018w119w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7b80de04…86d1
0x34b655…2a6f
6 touches
3 conflicts
0x76db6f00…325d
0x34b655…2a6f
4 touches
1 conflict
0x886cf9ba…604e
0x34b655…2a6f
4 touches
1 conflict
0x9b2105ea…29c0
0x34b655…2a6f
4 touches
1 conflict
0xa435dee8…f2be
0x34b655…2a6f
4 touches
1 conflict
0xafb2524a…0ce4
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity