← previous blocknext block →recent activity
Analyzing
Block #108,602,639
39 transactions · 27 stateful · 2026-09-28 00:00:09 UTC
Parallelism
90/100
Blocked
37%
Avg conflicts / tx
0.49
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,602,639 · 39 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
3w06w07w19w211w113w018w119w020w121w223w124w331w337w038w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x06e40499…165e
0x34ae4d…3fc5
6 touches
3 conflicts
0xa17ec269…7cdd
0x34ae4d…3fc5
6 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
6 touches
3 conflicts
0xc8525006…2b45
0x34ae4d…3fc5
6 touches
3 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: 0x125f12a1…cda50b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity