← previous blocknext block →recent activity
Analyzing
Block #99,854,743
25 transactions · 24 stateful · 2026-08-28 08:48:20 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,854,743 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w010w111w213w314w415w516w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28ab747a…02c3
0x34b655…2a6f
14 touches
21 conflicts
0xdb8288e3…7979
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
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
21 conflicts on slot 0x28ab747af3…4c02c3
Audit this contract →
← previous block·next block →recent activity