← previous blocknext block →recent activity
Analyzing
Block #100,617,370
22 transactions · 21 stateful · 2026-08-31 00:51:04 UTC
Parallelism
55/100
Blocked
57%
Avg conflicts / tx
1.91
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,617,370 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w48w59w610w711w815w917w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x0476d77b…a514
0x34b655…2a6f
6 touches
3 conflicts
0x09852bb8…22aa
0x34b655…2a6f
6 touches
3 conflicts
0x0ac16ad4…2493
0x34b655…2a6f
4 touches
1 conflict
0x168405e7…f38d
0x34b655…2a6f
4 touches
1 conflict
0x1e168c8b…6945
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x5e8223c2…c242
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity