← previous blocknext block →recent activity
Analyzing
Block #100,025,568
19 transactions · 18 stateful · 2026-08-28 23:09:05 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,025,568 · 19 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
1w02w13w04w15w07w08w19w210w312w213w415w516w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0490581d…adaf
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
8 touches
6 conflicts
0xf6e58332…a1a3
0x34b655…2a6f
8 touches
6 conflicts
0x61571888…b392
0x34b655…2a6f
6 touches
3 conflicts
0x9f77282b…47a2
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
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 0x0490581d5e…0badaf
Audit this contract →
← previous block·next block →recent activity