← previous blocknext block →recent activity
Analyzing
Block #100,056,016
17 transactions · 17 stateful · 2026-08-29 01:42:21 UTC
Parallelism
53/100
Blocked
65%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,056,016 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w08w19w210w211w312w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5871b087…587d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0xb240b520…a88a
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
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
10 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity