← previous blocknext block →recent activity
Analyzing
Block #100,618,205
14 transactions · 11 stateful · 2026-08-31 00:55:16 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,618,205 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w110w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebe581d8…2696
0x34b655…2a6f
6 touches
3 conflicts
0x29cd05f5…390c
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x4edbf2d2…36bc
0x34b655…2a6f
4 touches
1 conflict
0xade2f5e8…055a
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xebe581d8e8…f12696
Audit this contract →
← previous block·next block →recent activity