← previous blocknext block →recent activity
Analyzing
Block #94,749,948
19 transactions · 17 stateful · 2026-08-10 10:20:54 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,749,948 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w29w310w311w314w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
8 touches
6 conflicts
0xabb0951a…273a
0x34b655…2a6f
6 touches
3 conflicts
0xfb3eaa03…a56a
0x34b655…2a6f
6 touches
3 conflicts
0x24ca1902…7a87
0x34b655…2a6f
6 touches
3 conflicts
0x3230413b…bc7f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x5502e1cc19…1a3910
Audit this contract →
← previous block·next block →recent activity