← previous blocknext block →recent activity
Analyzing
Block #100,049,124
13 transactions · 13 stateful · 2026-08-29 01:07:40 UTC
Parallelism
46/100
Blocked
46%
Avg conflicts / tx
1.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,049,124 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w48w59w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2a76d80…ee44
0x34b655…2a6f
12 touches
15 conflicts
0xc1391924…967d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2b10b22f…4674
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xe062a6b0…b447
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
15 conflicts on slot 0xd2a76d80a7…41ee44
Audit this contract →
← previous block·next block →recent activity