← previous blocknext block →recent activity
Analyzing
Block #93,291,541
13 transactions · 11 stateful · 2026-08-05 07:49:32 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,291,541 · 13 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
3w06w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x109d18b7…997d
0x34b655…2a6f
2 touches
0 conflicts
0x2d9b1025…265b
0x34b655…2a6f
2 touches
0 conflicts
0x44614953…f05c
0x34b655…2a6f
2 touches
0 conflicts
0x450fb5b7…9760
0x34b655…2a6f
2 touches
0 conflicts
0x4b22966b…eef4
0x34b655…2a6f
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity