← previous blocknext block →recent activity
Analyzing
Block #106,272,028
19 transactions · 18 stateful · 2026-09-19 20:26:11 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
1.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,272,028 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w213w015w216w317w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10648fe8…cc34
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0x0fc536fb…1aa1
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xd41f5136…97c6
0x34b655…2a6f
6 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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: Perpl
6 conflicts on slot 0x10648fe8ad…19cc34
Audit this contract →
← previous block·next block →recent activity