← previous blocknext block →recent activity
Analyzing
Block #108,671,769
31 transactions · 25 stateful · 2026-09-28 05:48:18 UTC
Parallelism
87/100
Blocked
44%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,671,769 · 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
3w04w16w07w18w29w010w112w014w116w217w018w122w223w226w330w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x3859b4b7…b938
0xd32edf…ff58
5 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x1f3b37cb…357f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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: 0x125f12a1…cda50b
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity