← previous blocknext block →recent activity
Analyzing
Block #100,855,636
20 transactions · 18 stateful · 2026-08-31 20:50:02 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,855,636 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w110w211w113w215w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dca7cdd…b416
0x928dc8…8207
6 touches
3 conflicts
0x8dca7cdd…b418
0x928dc8…8207
6 touches
3 conflicts
0x613560f2…8d9e
0x928dc8…8207
6 touches
3 conflicts
0x6ede85f4…0b8a
0x928dc8…8207
6 touches
3 conflicts
0x6ede85f4…0b8b
0x928dc8…8207
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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: 0x928dc8af…fd8207
3 conflicts on slot 0x8dca7cddbf…48b416
Audit this contract →
← previous block·next block →recent activity