← previous blocknext block →recent activity
Analyzing
Block #100,732,329
19 transactions · 16 stateful · 2026-08-31 10:29:21 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,732,329 · 19 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
3w04w08w110w011w213w116w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
6 touches
3 conflicts
0xcdadad20…09a7
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9f4801c8…0afe
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 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity