← previous blocknext block →recent activity
Analyzing
Block #100,735,604
12 transactions · 11 stateful · 2026-08-31 10:45:49 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,735,604 · 12 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
4w06w17w08w19w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4db760d…fc5b
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x758f26d7…858f
0x01bff4…1071
4 touches
1 conflict
0xa8e98b9f…5935
0x01bff4…1071
4 touches
1 conflict
0x4213f1c0…219a
0x2a68ba…90c5
4 touches
1 conflict
0x05286dbb…4517
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
1 conflict on slot 0xf4db760d0a…f0fc5b
Audit this contract →
← previous block·next block →recent activity