← previous blocknext block →recent activity
Analyzing
Block #100,925,967
30 transactions · 26 stateful · 2026-09-01 02:43:48 UTC
Parallelism
83/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,925,967 · 30 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
3w04w15w26w39w010w012w014w115w116w217w219w320w422w423w128w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc73aa84c…ff9e
0x34b655…2a6f
10 touches
10 conflicts
0x25180879…8191
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0x8b10db95…0d05
0x34b655…2a6f
4 touches
1 conflict
0xb358a740…cf65
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 0xc73aa84c6b…08ff9e
Audit this contract →
← previous block·next block →recent activity