← previous blocknext block →recent activity
Analyzing
Block #100,029,643
17 transactions · 17 stateful · 2026-08-28 23:29:36 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,029,643 · 17 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
4w07w18w010w011w113w214w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3cbf2bf…04c0
0x34b655…2a6f
6 touches
3 conflicts
0x61571888…b392
0x34b655…2a6f
6 touches
3 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0e6f9f04…303f
0x34b655…2a6f
4 touches
1 conflict
0x2ad2f4bc…1800
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
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
3 conflicts on slot 0xa3cbf2bf0e…1e04c0
Audit this contract →
← previous block·next block →recent activity