← previous blocknext block →recent activity
Analyzing
Block #100,978,738
24 transactions · 22 stateful · 2026-09-01 07:09:15 UTC
Parallelism
92/100
Blocked
9%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,978,738 · 24 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
2w03w112w013w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x290abc80…f606
0x34b655…2a6f
4 touches
1 conflict
0x4582d65c…317e
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x809f2ba8…89d3
0x34b655…2a6f
4 touches
1 conflict
0x092fddd8…bcb7
0x34b655…2a6f
4 touches
1 conflict
0x290abc80…f605
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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 0x290abc804f…baf606
Audit this contract →
← previous block·next block →recent activity