← previous blocknext block →recent activity
Analyzing
Block #94,220,004
16 transactions · 13 stateful · 2026-08-08 13:42:22 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,220,004 · 16 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
4w05w18w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8982aa7…cbbf
0x34b655…2a6f
4 touches
1 conflict
0x522340e8…e6df
0x34b655…2a6f
4 touches
1 conflict
0x52aa1020…c85c
0x34b655…2a6f
4 touches
1 conflict
0x77efb543…f7c2
0x34b655…2a6f
4 touches
1 conflict
0x77efb543…f7c3
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0xbcab7dbe…2825
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xf8982aa77c…f1cbbf
Audit this contract →
← previous block·next block →recent activity