← previous blocknext block →recent activity
Analyzing
Block #100,629,410
22 transactions · 20 stateful · 2026-08-31 01:51:38 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,629,410 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w18w09w110w211w012w113w014w117w120w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa75029c…d62c
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x2734fe9c…068f
0x34b655…2a6f
4 touches
1 conflict
0x3a37aad1…720f
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x4e43e425…2678
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
6 conflicts on slot 0xfa75029c19…e9d62c
Audit this contract →
← previous block·next block →recent activity