← previous blocknext block →recent activity
Analyzing
Block #94,749,271
24 transactions · 21 stateful · 2026-08-10 10:17:25 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,749,271 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w39w010w111w412w513w616w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x2c4dfb12…6d78
0x34b655…2a6f
4 touches
1 conflict
0x420429ba…2582
0x34b655…2a6f
4 touches
1 conflict
0x4246172e…efab
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
6 conflicts on slot 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity