← previous blocknext block →recent activity
Analyzing
Block #94,814,093
19 transactions · 18 stateful · 2026-08-10 15:43:54 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,814,093 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w09w010w112w215w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x87ebdc37…8cad
0x34b655…2a6f
6 touches
3 conflicts
0xcc3678e9…76f7
0x34b655…2a6f
6 touches
3 conflicts
0xd83879b2…0bfb
0x34b655…2a6f
6 touches
3 conflicts
0x05527801…9c11
0x34b655…2a6f
6 touches
3 conflicts
0xef985cd1…f955
0x34b655…2a6f
6 touches
3 conflicts
0x28e5dbea…2f7f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity