← previous blocknext block →recent activity
Analyzing
Block #100,147,379
23 transactions · 18 stateful · 2026-08-29 09:22:29 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,147,379 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w19w213w314w417w519w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1681c4c…5858
0x34b655…2a6f
10 touches
10 conflicts
0xf98c943e…7c44
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb4a7c71b…0395
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3d3cd…7281
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 0xe1681c4c2a…9d5858
Audit this contract →
← previous block·next block →recent activity