← previous blocknext block →recent activity
Analyzing
Block #100,870,759
21 transactions · 18 stateful · 2026-08-31 22:06:06 UTC
Parallelism
90/100
Blocked
22%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,870,759 · 21 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
2w03w04w15w09w111w012w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2410d5d…8153
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0x9fbff0be…5314
0x34b655…2a6f
4 touches
1 conflict
0xb82f494f…db33
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0xf2410d5d8d…4e8153
Audit this contract →
← previous block·next block →recent activity