← previous blocknext block →recent activity
Analyzing
Block #94,663,138
13 transactions · 13 stateful · 2026-08-10 03:03:07 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,663,138 · 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
1w02w03w14w05w16w07w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bb15923…6698
0x851145…3f07
4 touches
1 conflict
0x72c8aeb2…9921
0x34b655…2a6f
4 touches
1 conflict
0x731998fc…c9a5
0x34b655…2a6f
4 touches
1 conflict
0xa351b7d0…8a20
0x34b655…2a6f
4 touches
1 conflict
0xa3f095f5…bd87
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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: 0x851145ea…9f3f07
1 conflict on slot 0x2bb1592331…806698
Audit this contract →
← previous block·next block →recent activity