← previous blocknext block →recent activity
Analyzing
Block #93,512,233
16 transactions · 16 stateful · 2026-08-06 02:19:05 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,512,233 · 16 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
2w06w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x03aa8b26…118a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x08dd3d…a583
2 touches
0 conflicts
0xff9eec93…1598
0x08dd3d…a583
2 touches
0 conflicts
0x00000000…0003
0x0a4fcb…a602
2 touches
0 conflicts
0xa6efaada…5869
0x0a4fcb…a602
2 touches
0 conflicts
0xc2575a0e…f876
0x0a4fcb…a602
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 0x4e8c4408ae…50d37b
Audit this contract →
← previous block·next block →recent activity