← previous blocknext block →recent activity
Analyzing
Block #100,432,611
14 transactions · 14 stateful · 2026-08-30 09:21:31 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,432,611 · 14 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
4w05w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
5 touches
3 conflicts
0x9c2b8525…f26d
0x34b655…2a6f
5 touches
3 conflicts
0x52cef1b0…0e4e
0x34b655…2a6f
4 touches
1 conflict
0x7aa5d2c4…d6ef
0x34b655…2a6f
4 touches
1 conflict
0x7e841543…7683
0x34b655…2a6f
4 touches
1 conflict
0x81cecfbe…6cf7
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
3 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity