← previous blocknext block →recent activity
Analyzing
Block #100,981,130
19 transactions · 18 stateful · 2026-09-01 07:21:17 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,981,130 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w07w111w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd814f518…f5b4
0x34b655…2a6f
10 touches
10 conflicts
0x6b4edd58…9623
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
4 touches
1 conflict
0x0cb37090…aee1
0x34b655…2a6f
4 touches
1 conflict
0x0f4998fe…6a62
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
10 conflicts on slot 0xd814f51828…c6f5b4
Audit this contract →
← previous block·next block →recent activity