← previous blocknext block →recent activity
Analyzing
Block #94,483,923
10 transactions · 8 stateful · 2026-08-09 12:01:44 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,483,923 · 10 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
2w03w14w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd44e517e…8d2f
0x34b655…2a6f
6 touches
3 conflicts
0xa8c5904c…e1a7
0x34b655…2a6f
4 touches
1 conflict
0x758a0dd5…0f46
0x34b655…2a6f
4 touches
1 conflict
0x9d6946b4…7f4e
0x34b655…2a6f
4 touches
1 conflict
0xa6176fff…d2c5
0x34b655…2a6f
4 touches
1 conflict
0x5224bec0…0675
0x34b655…2a6f
4 touches
1 conflict
0xe2263bea…6a9f
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6aa0
0x2b46c0…1669
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
3 conflicts on slot 0xd44e517e12…278d2f
Audit this contract →
← previous block·next block →recent activity