← previous blocknext block →recent activity
Analyzing
Block #93,556,741
13 transactions · 11 stateful · 2026-08-06 06:02:49 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,556,741 · 13 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
5w06w17w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x4727709a…4b57
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7ab9a682…f9ed
0x065c9d…c394
2 touches
0 conflicts
0x8fda21ce…0e27
0x065c9d…c394
2 touches
0 conflicts
0xaa449781…9946
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0x1bf8d2afa1…d2d140
Audit this contract →
← previous block·next block →recent activity