← previous blocknext block →recent activity
Analyzing
Block #93,663,351
13 transactions · 11 stateful · 2026-08-06 14:58:45 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,663,351 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0608dfe…083d
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0x30f02827…dd14
0x34b655…2a6f
2 touches
0 conflicts
0x31734e80…921f
0x34b655…2a6f
2 touches
0 conflicts
0x4c4c97a5…70e5
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 0xb0608dfe23…ab083d
Audit this contract →
← previous block·next block →recent activity