← previous blocknext block →recent activity
Analyzing
Block #100,612,575
27 transactions · 27 stateful · 2026-08-31 00:26:57 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,612,575 · 27 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
2w04w05w16w07w18w29w211w312w113w314w415w516w121w526w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58e6c68d…91be
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
8 touches
6 conflicts
0xee75c266…f8c6
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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 0x58e6c68d65…3f91be
Audit this contract →
← previous block·next block →recent activity