← previous blocknext block →recent activity
Analyzing
Block #100,145,959
15 transactions · 15 stateful · 2026-08-29 09:15:20 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,145,959 · 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
10w011w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8620ddb9…5114
0x8964d7…10f8
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x0e1d1106…f5b9
0x8964d7…10f8
4 touches
1 conflict
0x0e1d1106…f5ba
0x8964d7…10f8
4 touches
1 conflict
0x0e1d1106…f5bc
0x8964d7…10f8
4 touches
1 conflict
0x8620ddb9…510d
0x8964d7…10f8
4 touches
1 conflict
0x8620ddb9…510e
0x8964d7…10f8
4 touches
1 conflict
0x8620ddb9…5111
0x8964d7…10f8
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 0x8620ddb9e5…095114
Audit this contract →
← previous block·next block →recent activity