← previous blocknext block →recent activity
Analyzing
Block #94,224,507
13 transactions · 12 stateful · 2026-08-08 14:05:11 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,224,507 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6a5b44…d0e5
0x34b655…2a6f
4 touches
1 conflict
0x28d74e20…c54e
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x3969618f…86d0
0x34b655…2a6f
4 touches
1 conflict
0x3bab4355…fbfd
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x4d1d85aa…01a0
0x34b655…2a6f
4 touches
1 conflict
0x5b0b6826…ef3c
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
1 conflict on slot 0x0a6a5b4401…30d0e5
Audit this contract →
← previous block·next block →recent activity