← previous blocknext block →recent activity
Analyzing
Block #94,952,584
13 transactions · 12 stateful · 2026-08-11 03:20:30 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,952,584 · 13 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
2w03w14w26w07w18w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf2e1689…f33f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfc2493d3…6898
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x9c79b492…a68c
0x34b655…2a6f
4 touches
1 conflict
0xaea2f389…0305
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
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 0xdf2e168926…e6f33f
Audit this contract →
← previous block·next block →recent activity