← previous blocknext block →recent activity
Analyzing
Block #100,583,373
83 transactions · 62 stateful · 2026-08-30 22:00:02 UTC
Parallelism
77/100
Blocked
77%
Avg conflicts / tx
3.25
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #100,583,373 · 83 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w16w29w311w513w714w821w922w1023w1124w1225w1326w1439w242w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
32 touches
120 conflicts
0x889d5e90…929a
0x2a68ba…90c5
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x08d53462…97ef
0x2b46c0…1669
12 touches
15 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
12 touches
15 conflicts
0x7a12283f…b18a
0x2b46c0…1669
12 touches
15 conflicts
0x8b2c44b4…7e59
0x2b46c0…1669
12 touches
15 conflicts
0x915c095e…c1e5
0x2b46c0…1669
12 touches
15 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
120 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity