← previous blocknext block →recent activity
Analyzing
Block #100,461,420
22 transactions · 20 stateful · 2026-08-30 11:46:32 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,461,420 · 22 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
4w05w06w18w09w111w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58a9fce8…7f14
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f3a6b4a…3819
0x34b655…2a6f
2 touches
0 conflicts
0x7c9d9b4c…484d
0x34b655…2a6f
2 touches
0 conflicts
0x8046ca3c…f094
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 0x58a9fce879…d17f14
Audit this contract →
← previous block·next block →recent activity