← previous blocknext block →recent activity
Analyzing
Block #105,549,847
15 transactions · 13 stateful · 2026-09-17 07:48:54 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,549,847 · 15 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b595a5d…894c
0x34b655…2a6f
8 touches
6 conflicts
0x3b73e5ed…6ff5
0x34b655…2a6f
8 touches
6 conflicts
0x0eac7709…66c3
0x34b655…2a6f
6 touches
3 conflicts
0x19795ad6…4a16
0x34b655…2a6f
6 touches
3 conflicts
0xc3706e68…1f19
0x34b655…2a6f
4 touches
1 conflict
0x2a4dbf69…22c2
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
6 conflicts on slot 0x6b595a5d7d…1f894c
Audit this contract →
← previous block·next block →recent activity