← previous blocknext block →recent activity
Analyzing
Block #100,562,491
20 transactions · 17 stateful · 2026-08-30 20:15:00 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,562,491 · 20 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
1w02w13w08w111w012w113w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
16 touches
28 conflicts
0xbd590df7…9891
0x34b655…2a6f
16 touches
28 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x5d3edf37…6e51
0x34b655…2a6f
6 touches
3 conflicts
0x1d1eb3d2…d573
0x34b655…2a6f
5 touches
3 conflicts
0x26489242…c321
0x34b655…2a6f
4 touches
1 conflict
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
28 conflicts on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity