← previous blocknext block →recent activity
Analyzing
Block #100,125,448
22 transactions · 20 stateful · 2026-08-29 07:31:56 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,125,448 · 22 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
8w09w110w211w312w415w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bc17c3c…aa77
0x34b655…2a6f
8 touches
6 conflicts
0x2a07e64e…fe77
0x754704…b603
8 touches
6 conflicts
0x00000000…0008
0x8964d7…10f8
8 touches
6 conflicts
0x2a4f0eab…e293
0x8964d7…10f8
6 touches
3 conflicts
0x2a4f0eab…e294
0x8964d7…10f8
6 touches
3 conflicts
0x2a4f0eab…e296
0x8964d7…10f8
6 touches
3 conflicts
0xf5b2d0c4…df30
0x8964d7…10f8
6 touches
3 conflicts
0x6415c9bf…6c16
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
6 conflicts on slot 0x1bc17c3cee…7faa77
Audit this contract →
← previous block·next block →recent activity