← previous blocknext block →recent activity
Analyzing
Block #100,984,379
18 transactions · 17 stateful · 2026-09-01 07:37:37 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,984,379 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w09w110w011w112w214w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc89b9352…81fb
0x34b655…2a6f
6 touches
3 conflicts
0x54c6fb44…369a
0x34b655…2a6f
6 touches
3 conflicts
0xd7443f37…eb79
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x75311cd9…b360
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x34ae4d…3fc5
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
3 conflicts on slot 0xc89b935255…5481fb
Audit this contract →
← previous block·next block →recent activity