← previous blocknext block →recent activity
Analyzing
Block #100,063,388
17 transactions · 10 stateful · 2026-08-29 02:19:27 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,063,388 · 17 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
7w09w110w212w013w314w415w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2a76d80…ee44
0x34b655…2a6f
8 touches
6 conflicts
0x030939d3…a0eb
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0x8f985aa6…5f12
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xf72228f6…970c
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
6 conflicts on slot 0xd2a76d80a7…41ee44
Audit this contract →
← previous block·next block →recent activity