← previous blocknext block →recent activity
Analyzing
Block #100,747,501
14 transactions · 13 stateful · 2026-08-31 11:45:40 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,747,501 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89ac61bf…9443
0x34b655…2a6f
6 touches
3 conflicts
0xfa5b7f1e…5338
0x34b655…2a6f
4 touches
1 conflict
0x68531239…e9a3
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x1a6c1a40…114e
0x34b655…2a6f
2 touches
0 conflicts
0x20f33909…299e
0x34b655…2a6f
2 touches
0 conflicts
0x5947e5b2…3625
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x89ac61bf64…6b9443
Audit this contract →
← previous block·next block →recent activity