← previous blocknext block →recent activity
Analyzing
Block #100,130,152
24 transactions · 23 stateful · 2026-08-29 07:55:36 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,130,152 · 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
2w04w111w013w215w120w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe226a0be…c046
0x34b655…2a6f
4 touches
1 conflict
0x243d2cc1…b91d
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x50812214…4dcd
0x34b655…2a6f
4 touches
1 conflict
0x5ecbbe42…e861
0x34b655…2a6f
4 touches
1 conflict
0x5ed1f9d0…fc7f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb7e8b0c4…dec3
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 0xe226a0be4d…4bc046
Audit this contract →
← previous block·next block →recent activity