← previous blocknext block →recent activity
Analyzing
Block #94,862,442
26 transactions · 22 stateful · 2026-08-10 19:47:08 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,862,442 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w011w012w114w015w116w021w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x9a7d4d9b…3898
0x40c49f…2af0
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x26040a51…4b8c
0x34b655…2a6f
4 touches
1 conflict
0x339e553b…ba52
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
1 conflict on slot 0xd6113c0f7f…b30a4b
Audit this contract →
← previous block·next block →recent activity