← previous blocknext block →recent activity
Analyzing
Block #100,049,156
19 transactions · 16 stateful · 2026-08-29 01:07:49 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,049,156 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w08w015w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x030939d3…a0eb
0x34b655…2a6f
6 touches
3 conflicts
0xd5c98027…9fd9
0x34b655…2a6f
4 touches
1 conflict
0xd2a76d80…ee44
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0e543387…38e5
0xd32edf…ff58
3 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
3 conflicts on slot 0x030939d3cd…65a0eb
Audit this contract →
← previous block·next block →recent activity