← previous blocknext block →recent activity
Analyzing
Block #100,601,287
57 transactions · 33 stateful · 2026-08-30 23:30:09 UTC
Parallelism
79/100
Blocked
73%
Avg conflicts / tx
1.68
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #100,601,287 · 57 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w112w013w114w015w116w217w318w419w521w622w724w225w327w228w829w930w1031w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x10d80fee…dbda
0x2b46c0…1669
8 touches
6 conflicts
0x40970e69…da50
0x2b46c0…1669
8 touches
6 conflicts
0x55012d1a…3907
0x2b46c0…1669
8 touches
6 conflicts
0xad3ef711…4f2b
0x2b46c0…1669
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 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: 0xf5b5f7f8…a36d70
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity