← previous blocknext block →recent activity
Analyzing
Block #100,891,694
17 transactions · 15 stateful · 2026-08-31 23:51:25 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,891,694 · 17 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
4w012w013w114w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x353fc724…f222
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb1a84f54…bb64
0x34b655…2a6f
4 touches
1 conflict
0xe26c4e53…94c2
0x34b655…2a6f
4 touches
1 conflict
0xe26c4e53…94c3
0x34b655…2a6f
4 touches
1 conflict
0xf42241ea…092b
0x34b655…2a6f
4 touches
1 conflict
0x28619e76…41e4
0x34b655…2a6f
4 touches
1 conflict
0x9857a895…4e15
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 0x353fc724f7…b1f222
Audit this contract →
← previous block·next block →recent activity