← previous blocknext block →recent activity
Analyzing
Block #94,202,921
17 transactions · 16 stateful · 2026-08-08 12:15:51 UTC
Parallelism
59/100
Blocked
38%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,202,921 · 17 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
1w02w13w05w26w37w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xab924b05…e1b6
0x34b655…2a6f
8 touches
6 conflicts
0xe2e52e46…0894
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xcffc17bc…3544
0x34b655…2a6f
6 touches
3 conflicts
0x69a5f48e…f3c3
0x34b655…2a6f
4 touches
1 conflict
0x77efb543…f7c2
0x34b655…2a6f
4 touches
1 conflict
0x77efb543…f7c3
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity