← previous blocknext block →recent activity
Analyzing
Block #100,983,704
19 transactions · 17 stateful · 2026-09-01 07:34:14 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,983,704 · 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
5w07w08w09w110w111w213w014w116w317w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf91dc591…97cd
0x34b655…2a6f
8 touches
6 conflicts
0x8b7fe709…9d99
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
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
6 conflicts on slot 0xf91dc59153…2197cd
Audit this contract →
← previous block·next block →recent activity