← previous blocknext block →recent activity
Analyzing
Block #100,585,453
15 transactions · 13 stateful · 2026-08-30 22:10:30 UTC
Parallelism
87/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,585,453 · 15 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
6w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6500c931…dd16
0x8964d7…10f8
4 touches
1 conflict
0x6500c931…dd10
0x8964d7…10f8
4 touches
1 conflict
0x6500c931…dd11
0x8964d7…10f8
4 touches
1 conflict
0x6500c931…dd14
0x8964d7…10f8
4 touches
1 conflict
0x6500c931…dd15
0x8964d7…10f8
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x952dd1d7…897a
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x6500c931c4…f1dd16
Audit this contract →
← previous block·next block →recent activity