← previous blocknext block →recent activity
Analyzing
Block #100,104,020
23 transactions · 21 stateful · 2026-08-29 05:44:01 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,104,020 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w18w210w011w112w213w317w418w520w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86c070aa…40c8
0x34b655…2a6f
10 touches
10 conflicts
0x53103bb4…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2eb75a72…0654
0x34b655…2a6f
6 touches
3 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x9c3004b2…5421
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
10 conflicts on slot 0x86c070aa21…4140c8
Audit this contract →
← previous block·next block →recent activity