← previous blocknext block →recent activity
Analyzing
Block #100,047,803
24 transactions · 23 stateful · 2026-08-29 01:01:01 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,047,803 · 24 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
3w04w19w010w111w212w313w019w120w422w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eb20016…eb59
0x34b655…2a6f
10 touches
10 conflicts
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
8 touches
6 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
8 touches
6 conflicts
0x2d4cd1ab…19b0
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xa18d515f…b4de
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x5eb20016be…a0eb59
Audit this contract →
← previous block·next block →recent activity