← previous blocknext block →recent activity
Analyzing
Block #108,366,408
13 transactions · 13 stateful · 2026-09-27 04:10:53 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,366,408 · 13 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
1w02w03w17w19w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x9f46452e…9840
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x37f93b32…cc57
0x34b655…2a6f
4 touches
1 conflict
0xd5bbe73a…b70d
0x34b655…2a6f
4 touches
1 conflict
0xbf70d3be…8ecc
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 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity