← previous blocknext block →recent activity
Analyzing
Block #100,083,343
23 transactions · 19 stateful · 2026-08-29 03:59:55 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,083,343 · 23 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
1w05w06w18w111w212w314w017w418w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6370b2a…08cb
0x34b655…2a6f
8 touches
6 conflicts
0x627738d1…db02
0x34b655…2a6f
8 touches
6 conflicts
0xfc81faf7…1417
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x3dc720a7…59c3
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
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 0xd6370b2a50…cd08cb
Audit this contract →
← previous block·next block →recent activity