← previous blocknext block →recent activity
Analyzing
Block #100,054,762
13 transactions · 13 stateful · 2026-08-29 01:36:02 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,054,762 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x7083c381…0ce7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xbd590df7f7…cf9891
Audit this contract →
← previous block·next block →recent activity