← previous blocknext block →recent activity
Analyzing
Block #93,579,194
14 transactions · 13 stateful · 2026-08-06 07:55:41 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,579,194 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x378c030c…a8a4
0x34b655…2a6f
6 touches
3 conflicts
0x98212952…9ba6
0x34b655…2a6f
6 touches
3 conflicts
0x01c7fc4c…6445
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x79fb7a0a…b57a
0x34b655…2a6f
4 touches
1 conflict
0x90c0594a…5f65
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
3 conflicts on slot 0x378c030cda…2ba8a4
Audit this contract →
← previous block·next block →recent activity