← previous blocknext block →recent activity
Analyzing
Block #100,923,223
25 transactions · 22 stateful · 2026-09-01 02:30:00 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,923,223 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w09w110w214w015w119w120w223w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735ca879…67e8
0x34b655…2a6f
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0x16586648…476a
0x34b655…2a6f
4 touches
1 conflict
0x216e917f…d077
0x34b655…2a6f
4 touches
1 conflict
0xfb856b8c…7557
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 0x735ca879d2…5067e8
Audit this contract →
← previous block·next block →recent activity