← previous blocknext block →recent activity
Analyzing
Block #94,914,382
17 transactions · 16 stateful · 2026-08-11 00:08:21 UTC
Parallelism
82/100
Blocked
19%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,914,382 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x378c030c…a8a4
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x90c0594a…5f65
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a5
0x34b655…2a6f
4 touches
1 conflict
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0x3b64087e…3af6
0x34b655…2a6f
3 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 0x378c030cda…2ba8a4
Audit this contract →
← previous block·next block →recent activity