← previous blocknext block →recent activity
Analyzing
Block #94,914,249
15 transactions · 13 stateful · 2026-08-11 00:07:40 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,914,249 · 15 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
1w02w13w04w15w06w17w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x758f26d7…858f
0x01bff4…1071
4 touches
1 conflict
0xa8e98b9f…5935
0x01bff4…1071
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xb726505b…f6bd
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
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 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity