← previous blocknext block →recent activity
Analyzing
Block #100,851,492
27 transactions · 22 stateful · 2026-08-31 20:29:12 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,851,492 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w115w116w217w318w226w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c1dadfb…ba28
0x34b655…2a6f
6 touches
3 conflicts
0xfc8d572c…b27d
0x34b655…2a6f
6 touches
3 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
4 touches
1 conflict
0xd0559397…64e9
0x34b655…2a6f
4 touches
1 conflict
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0xfc4873a8…9112
0x34b655…2a6f
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x50e84e6c…287f
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 0x8c1dadfb6c…4eba28
Audit this contract →
← previous block·next block →recent activity