← previous blocknext block →recent activity
Analyzing
Block #94,798,663
21 transactions · 20 stateful · 2026-08-10 14:26:16 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,798,663 · 21 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
2w03w04w05w16w17w08w111w212w313w014w216w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x9183a0c5…2cbb
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity