← previous blocknext block →recent activity
Analyzing
Block #100,922,869
24 transactions · 21 stateful · 2026-09-01 02:28:13 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,922,869 · 24 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
1w02w16w010w013w014w115w216w219w121w223w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51f05f20…36a4
0x34b655…2a6f
6 touches
3 conflicts
0xc8f28e8d…61e6
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xffb8950c…23c6
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0x51f05f20f3…1636a4
Audit this contract →
← previous block·next block →recent activity