← previous blocknext block →recent activity
Analyzing
Block #100,124,194
26 transactions · 22 stateful · 2026-08-29 07:25:37 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,124,194 · 26 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
1w02w03w07w08w112w213w314w415w117w119w120w522w625w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x549c2377…ad00
0x34b655…2a6f
10 touches
10 conflicts
0x627738d1…db02
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
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 0x549c2377aa…13ad00
Audit this contract →
← previous block·next block →recent activity