← previous blocknext block →recent activity
Analyzing
Block #100,433,681
17 transactions · 16 stateful · 2026-08-30 09:26:54 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,433,681 · 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
1w02w18w010w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4db508b8…b746
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb0e974c4…b84d
0x34b655…2a6f
6 touches
3 conflicts
0x05286dbb…4517
0x34b655…2a6f
4 touches
1 conflict
0x0aa5e418…5d1d
0x34b655…2a6f
4 touches
1 conflict
0x24e6ab11…e317
0x34b655…2a6f
4 touches
1 conflict
0x2f5caafc…3ea1
0x34b655…2a6f
4 touches
1 conflict
0x3701af3b…2d51
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 0x4db508b8cf…f8b746
Audit this contract →
← previous block·next block →recent activity