← previous blocknext block →recent activity
Analyzing
Block #100,894,657
22 transactions · 21 stateful · 2026-09-01 00:06:19 UTC
Parallelism
91/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,894,657 · 22 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
3w04w19w010w011w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfa09be5a…1e79
0x34b655…2a6f
4 touches
1 conflict
0x27c8497b…dcc4
0x754704…b603
4 touches
1 conflict
0x87c3dfca…7ce9
0x754704…b603
4 touches
1 conflict
0xbb95fb3e…c47b
0x754704…b603
4 touches
1 conflict
0x5f28dff7…3ddd
0x99c7a7…8bf0
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
1 conflict on slot 0x4a5956ef63…f0e226
Audit this contract →
← previous block·next block →recent activity