← previous blocknext block →recent activity
Analyzing
Block #100,631,810
23 transactions · 20 stateful · 2026-08-31 02:03:43 UTC
Parallelism
78/100
Blocked
55%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,631,810 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w18w010w211w112w213w114w216w317w018w119w121w422w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc545fdad…74de
0x851145…3f07
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x352c45ab…a8ee
0x851145…3f07
6 touches
3 conflicts
0x6a0638a3…fc78
0x851145…3f07
6 touches
3 conflicts
0xc9c17729…ac91
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: 0x851145ea…9f3f07
3 conflicts on slot 0xc545fdada0…0e74de
Audit this contract →
← previous block·next block →recent activity