← previous blocknext block →recent activity
Analyzing
Block #94,129,345
21 transactions · 21 stateful · 2026-08-08 06:03:01 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,129,345 · 21 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
1w04w05w16w09w010w111w212w113w114w215w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2df168a5…cc6c
0x34b655…2a6f
6 touches
3 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
6 touches
3 conflicts
0x500f03d6…a4c4
0xa6afd3…d132
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca3f1796…927c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0x2df168a590…dccc6c
Audit this contract →
← previous block·next block →recent activity