← previous blocknext block →recent activity
Analyzing
Block #100,151,932
14 transactions · 13 stateful · 2026-08-29 09:45:24 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,151,932 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5ec4c01…9d44
0x34b655…2a6f
4 touches
1 conflict
0x2bb0d58d…9dcf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xaa072b82…3ddd
0x34b655…2a6f
4 touches
1 conflict
0x8d7544e2…641c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x3df6122f…fba3
0x34b655…2a6f
3 touches
1 conflict
0x6d5d1fb5…86a7
0x34b655…2a6f
2 touches
0 conflicts
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 0xd5ec4c01b9…059d44
Audit this contract →
← previous block·next block →recent activity