← previous blocknext block →recent activity
Analyzing
Block #100,812,424
25 transactions · 21 stateful · 2026-08-31 17:12:28 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,812,424 · 25 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
2w05w06w114w015w116w117w120w123w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa538600d…3da5
0x851145…3f07
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x80b23975…a7bf
0x34b655…2a6f
4 touches
1 conflict
0x9a100e05…c541
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: 0x851145ea…9f3f07
1 conflict on slot 0xa538600de5…683da5
Audit this contract →
← previous block·next block →recent activity