← previous blocknext block →recent activity
Analyzing
Block #100,057,080
15 transactions · 15 stateful · 2026-08-29 01:47:42 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,057,080 · 15 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
1w04w15w06w18w09w112w213w014w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0x79d2045a…29c4
0x34b655…2a6f
6 touches
3 conflicts
0x09e0690d…6e3d
0xe52b14…7230
4 touches
1 conflict
0x17bbe4f8…08c5
0xe52b14…7230
4 touches
1 conflict
0x3cebc8f1…975c
0xe52b14…7230
4 touches
1 conflict
0x58733c38…f2cd
0xe52b14…7230
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity