← previous blocknext block →recent activity
Analyzing
Block #100,923,604
17 transactions · 14 stateful · 2026-09-01 02:31:55 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,923,604 · 17 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
1w02w15w08w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb424877f…ef89
0x34b655…2a6f
4 touches
1 conflict
0xdc9915b5…542c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7d694220…0423
0x065c9d…c394
2 touches
0 conflicts
0xe1800937…071b
0x065c9d…c394
2 touches
0 conflicts
0xf1ee5e63…6aa2
0x065c9d…c394
2 touches
0 conflicts
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
1 conflict on slot 0xb424877f5a…87ef89
Audit this contract →
← previous block·next block →recent activity