← previous blocknext block →recent activity
Analyzing
Block #103,049,998
31 transactions · 22 stateful · 2026-09-08 13:21:44 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,049,998 · 31 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
2w05w06w19w210w011w012w121w323w226w027w128w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xf856bb44…f106
0x065c9d…c394
5 touches
3 conflicts
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity