← previous blocknext block →recent activity
Analyzing
Block #94,318,787
20 transactions · 20 stateful · 2026-08-08 22:03:08 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,318,787 · 20 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
2w03w04w15w26w17w28w39w013w014w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1f90c45d…89c3
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x62efcbc7…c7e7
0x34b655…2a6f
4 touches
1 conflict
0x9a2a78fa…382a
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity