← previous blocknext block →recent activity
Analyzing
Block #94,847,144
19 transactions · 19 stateful · 2026-08-10 18:30:11 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.89
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,847,144 · 19 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
1w02w13w24w35w46w58w69w713w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x324cb18b…bcc6
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
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
10 conflicts on slot 0x324cb18bda…b5bcc6
Audit this contract →
← previous block·next block →recent activity