← previous blocknext block →recent activity
Analyzing
Block #100,604,310
21 transactions · 19 stateful · 2026-08-30 23:45:22 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,604,310 · 21 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
3w04w16w07w110w211w312w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3644f89…29eb
0x34b655…2a6f
8 touches
6 conflicts
0x627738d1…db02
0x34b655…2a6f
6 touches
3 conflicts
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x341e01be…240c
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0xa3644f898f…7729eb
Audit this contract →
← previous block·next block →recent activity