← previous blocknext block →recent activity
Analyzing
Block #94,465,359
10 transactions · 9 stateful · 2026-08-09 10:28:19 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,465,359 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22866298…d604
0x34b655…2a6f
8 touches
6 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0xa6311649…0132
0x34b655…2a6f
4 touches
1 conflict
0xa6389d47…9a28
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9e1a89c0…fe4e
0x065c9d…c394
2 touches
0 conflicts
0xeece21b9…1fa2
0x065c9d…c394
2 touches
0 conflicts
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 0x2286629889…9ed604
Audit this contract →
← previous block·next block →recent activity