← previous blocknext block →recent activity
Analyzing
Block #100,433,395
17 transactions · 16 stateful · 2026-08-30 09:25:28 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,433,395 · 17 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
5w06w17w18w211w312w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x005321e0…2e05
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xd793c15e…7dba
0x34b655…2a6f
4 touches
1 conflict
0x48e2bdf3…b545
0x34b655…2a6f
4 touches
1 conflict
0xa47b7766…ee6e
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xbceecf11…0120
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 0x005321e088…9c2e05
Audit this contract →
← previous block·next block →recent activity