← previous blocknext block →recent activity
Analyzing
Block #100,740,038
23 transactions · 21 stateful · 2026-08-31 11:08:07 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,740,038 · 23 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
2w06w07w09w110w011w114w015w116w217w119w221w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8814d787…b4fd
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x3b674eb1…4635
0x851145…3f07
6 touches
3 conflicts
0xd9722304…6ed0
0x34b655…2a6f
6 touches
3 conflicts
0x11b69a7e…334e
0x01bff4…1071
6 touches
3 conflicts
0xa5071ca5…717b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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: Perpl
3 conflicts on slot 0x8814d78793…16b4fd
Audit this contract →
← previous block·next block →recent activity