← previous blocknext block →recent activity
Analyzing
Block #105,376,516
22 transactions · 21 stateful · 2026-09-16 17:16:28 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,376,516 · 22 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
1w02w13w05w06w18w09w112w115w217w218w320w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad82682f…71e2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x570bf5da…6a77
0x34b655…2a6f
4 touches
1 conflict
0x76e994db…0a69
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 0xad82682f72…0a71e2
Audit this contract →
← previous block·next block →recent activity