← previous blocknext block →recent activity
Analyzing
Block #94,816,501
21 transactions · 18 stateful · 2026-08-10 15:56:00 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,816,501 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w26w17w38w212w413w514w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8bc53a3…c2fe
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xa7f92fce…e881
0x34b655…2a6f
6 touches
3 conflicts
0x3d158563…8713
0x34b655…2a6f
6 touches
3 conflicts
0xaea268e5…6731
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 0xd8bc53a346…42c2fe
Audit this contract →
← previous block·next block →recent activity