← previous blocknext block →recent activity
Analyzing
Block #93,678,689
11 transactions · 11 stateful · 2026-08-06 16:15:52 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,678,689 · 11 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
3w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50dbe610…177f
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x4e50038e…6e29
0x34b655…2a6f
4 touches
1 conflict
0xb62f9ca2…1f69
0x065c9d…c394
3 touches
1 conflict
0x334aa47d…cac0
0x34b655…2a6f
2 touches
0 conflicts
0x59bfb0ed…ebd2
0x34b655…2a6f
2 touches
0 conflicts
0x60dc7b78…d1d5
0x34b655…2a6f
2 touches
0 conflicts
0x65afec8b…2626
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 0x50dbe61059…f8177f
Audit this contract →
← previous block·next block →recent activity